nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

New Observation when adding DATUM in component in a Group doesnt reflect on Update

sgarimella

I am facing a strange issue and I am not sure if this is the correct behavior.
The scenario is:
I introduce a new DATUM in a Group of a component. This new DATUM does not reflect on the Page using the component on "Update". The component needs to be Overwritten for the change to appear.

Snippet from Content XML of a component is attached...

Another Observation:

If a new DATUM is introduced outside a GROUP. On Update the component is reflected on the Page using the component.

Has anyone faced anything like this?
Any pointers are most welcomed...

TS Version: 7.1

Find more posts tagged with

Comments

acezone

I am facing a strange issue and I am not sure if this is the correct behavior.
The scenario is:
I introduce a new DATUM in a Group of a component. This new DATUM does not reflect on the Page using the component on "Update". The component needs to be Overwritten for the change to appear.

Snippet from Content XML of a component is attached...

Another Observation:

If a new DATUM is introduced outside a GROUP. On Update the component is reflected on the Page using the component.

Has anyone faced anything like this?
Any pointers are most welcomed...

TS Version: 7.1

Hi sgarimella,

Once the component is placed on the page, I would like to know if this component is edited with replicants. If yes, then Update option then shall only be updating the content but new Datum is more as an item associated to Group, so that may not be visible.

Logic is such that, with replicated Group with CloneID will only work on component level but in order to make the new Datum available on page it is always required to Overwrite component so that it should first be restored to its original state and then it'll be available with new CloneID.

Try this instead to debug this issue, download page to local system and remove edited code done on the page and make sure, component Content XML and code on page shall be similar. Upload page back to TeamSite, start editing page as normal practice. It may prompt you for Overwite / Update option. Select Update, and you'll then see that a newly added Datum shall then be appeared in component properties window.

Let me know your findings and if required please feel free to update thread with your comments.

Regards,
Ace

sgarimella

Hi acezone,

Thanks, you have helped me learn a new point.

Whenever I add/remove a new DATUM to a replicatable group in a component, a new cloneID is generated in the component.

For the new cloneID is reflected on the page only on Component Overwrite and not Update. Then the replicatable group change gets reflected on the Page.

The page technique which you said is working.

If there is any gap in my understanding, let me know.

Thanks,
Sudha.

acezone

Hi acezone,

Thanks, you have helped me learn a new point.

Whenever I add/remove a new DATUM to a replicatable group in a component, a new cloneID is generated in the component.

For the new cloneID is reflected on the page only on Component Overwrite and not Update. Then the replicatable group change gets reflected on the Page.

The page technique which you said is working.

If there is any gap in my understanding, let me know.

Thanks,
Sudha.

Glad to be help for you.

Regards,
Ace