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; } } }

Updating dropdown values in content XML dynamically

Natasha

Hi All

I have a requirement wherein I want to update the dropdown values dynamically in the content XML without modifying the component code.
Everytime a change is requested by the content authors in the dropdown values, a component needs to be updated which requires a code release and takes around a week for the change to be available for content authors.
So we are just analysing if a workaround is available wherein the component change can be avoided.
Looking forward to inputs/suggestions.

Thanks
Natasha.
Env details - TS 6.7.1, LS 3.0

Find more posts tagged with

Comments

vpatel

Sounds like you need Generators in your component.

Natasha

Sounds like you need Generators in your component.

Thanks for your response. Could you please elaborate on this, I couldn't find much about the generatord in the SP dev manual.
I would appreciate if you could share the way you have used generators as per your requirement.

Thanks
Natasha.

PayalGarg

You can find this at page 198 in SP Guide.

[HTML]

5

[/HTML]

Regards
Payal

Adam Stoller

Please learn how to properly format and Preview your posts - the tag for rendering HTML/XML content is

[html]...[/html]

not

[HTML]...[/HTML]

You can find this at page 198 in SP Guide.

[html]

5

[/html]

Regards
Payal

PayalGarg

But I used the one provided in the editor itself....one with the tooltip that says "Wrap [HTML] tags around selected text".

Adam Stoller

But I used the one provided in the editor itself....one with the tooltip that says "Wrap [HTML] tags around selected text".

Apparently it's a WYSINWYG editor :-)
Send email to Autonomy to complain...?

Natasha

Thanks payal.
Could you please confirm which version of LS did you find this information in?
On page 198 - LS 3.0 SP1 dev, Externals have been explained, there is no usage of Generators explained there. However, I found another way of building dynamic options which is through "PropertyPrefix" which alters the contents of Datums dynamically.

PayalGarg

I checked in SP dev guide version 3.1. Later I realized that this is not in SP Guide 3.0.

Per SP dev guide ver 3.1

Generator is a way to insert data as a peer node. The code is executed and parameters are passed in. The result is appended as a peer node. This is used to dynamically alter the contents of a Datum.
[font=Verdana][color=black]

Per SP dev guide ver 3.0

[/font][/color]PropertyPrefix is a way to insert data as a peer node. The code is executed and parameters are passed in, the result is appended as a peer node. This is useful in dynamically altering the contents of a Datum.

I think the only change is in terminology.... Smiley Wink

Natasha

I checked in SP dev guide version 3.1. Later I realized that this is not in SP Guide 3.0.

Per SP dev guide ver 3.1
Generator is a way to insert data as a peer node. The code is executed and parameters are passed in. The result is appended as a peer node. This is used to dynamically alter the contents of a Datum.
[font=Verdana][color=black]

Per SP dev guide ver 3.0
[/font][/color]PropertyPrefix is a way to insert data as a peer node. The code is executed and parameters are passed in, the result is appended as a peer node. This is useful in dynamically altering the contents of a Datum.

I think the only change is in terminology....

Thanks, PropertyPrefix worked in my case Smiley Happy

However on editing the component, a warning message appears in the content XML tab which says :-
"One or more properties (marked in red below) were automatically updated because their current value was out of sync with the available values. To save the updated values click the Apply button below" which I suppose appears in LS 3.1 as well. Would be great if you can confirm.

Thanks
Natasha.

PayalGarg

This appears because no default value is set for the datum SelectSingle. Try to set some default value while previewing the component. Once you have set a value then that warning will not appear anymore and you will see following code added to your Content XML.

[html]

5

New
n

[/html]

Natasha

This appears because no default value is set for the datum SelectSingle. Try to set some default value while previewing the component. Once you have set a value then that warning will not appear anymore and you will see following code added to your Content XML.

[html]

5

New
n

[/html]

I have set the option as selected="true" but I am still getting this warning message.
[HTML]

5

Author
xyz

[/HTML]

I think we need to add selected="true" to option values returned by External.
Are you doing the same in your external class?

PayalGarg

I think, If the value that you are speciying as default is not returned by your external, then you will get the warning. In your case, if the value "xyz" is not returned by your external and is therefore not in the list of options returned by the external, then only you should get this warning.

[html]
Author
xyz
[/html]

I'm generating the list options as:

[left][html] option.addElement("Display").addText("new");[/left]
option.addElement("Value").addText("n");[/html]

Please post back your inputs.

Natasha

It worked, thanks Payal for helping me with this Smiley Happy