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

what is best approach to update Multivalue Attribut Fields by OScript?

Thomas Heusser

Issue: updating as i use it until now works fine, if there are similar amount of new Values or more.

If there are less new Attributs, the last ones remains in the Category.

Thomas

Find more posts tagged with

Comments

Hans Stoop

Hi Thomas,

The value of an attribute is a list of values. Just assign theValues field the list with all your values.

Hans

From: eLink Entry:Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Freitag, 17. September 2010 16:27
To: eLink Recipient
Subject: what is best approach to update Multivalue Attribut Fields byOScript?

what is best approach to update Multivalue Attribut Fields by OScript?

Posted by theusser (Heusser, Thomas) On 2010/09/17 10:24

what is best approach to update Multivalue Attribut Fields by OScript?

Issue: updating as i use it until now works fine, if there are similar amount of new Values or more.

If there are less new Attributs, the last ones remains in the Category.

Thomas

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Livelink Server:	knowledge-wlweb01

Thomas Heusser

Hallo Hans,

thank you, first i thought, it's solved like your proposal, but now by testing, there are two issues comming up:

- if there is no conent in the Mulitvaluefield, also the empty field is missing (and also the + Icon to add new values) but without error. I tried different settings eg like

       a) empty list
       b) Assoc.CreateAssoc(Assoc.NotSetValue())
       c) empty String

and it loosk like this ("Dfa-Linie", "Kilometer von:", "Kilometer bis" are empty Mulitivalue Fields):

- if there are values (one or multiple), all "looks" ok, but if someone would like to add or remove a Multivaluefield, i get this error by clicking the + Icon:

I use this code

any idea what could go wrong?

thomas

Hans Stoop

Hi Thomas,

When you don’t have a value then you should assign {UNDEFINED}(….values = {UNDEFINED}).

In general you should have in your code ….values = {value1,value2, value3}

Hans

From: eLink Entry:Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Dienstag, 21. September 2010 18:25
To: eLink Recipient
Subject: RE what is best approach to update Multivalue Attribut Fieldsby OScript?

RE what is best approach to update Multivalue Attribut Fields by OScript?

Posted by theusser (Heusser, Thomas) On 2010/09/21 12:23

Hallo Hans,

thank you, first i thought, it's solved like your proposal, but now by testing, there are two issues comming up:

- if there is no conent in the Mulitvaluefield, also the empty field is missing (and also the + Icon to add new values) but without error. I settings like this

       a) empty list
       b) Assoc.CreateAssoc(Assoc.NotSetValue())
       c) empty String

and it loosk like this:

(image)

- if there are values (one or multiple), all "looks" ok, but if someone would like to add or remove a Multivaluefield, i get this error:

(image)

I use t! his code

(image)

any idea what could go wrong?

thomas

[To post a comment, use the normal reply function]
Topic:	what is best approach to update Multivalue Attribut Fields by OScript?
Forum:	Content Server Development Forum
Livelink Server:	knowledge-wlweb01

Thomas Heusser

Thank you Hans, multiValues = {UNDEFINED} does it

i use now with success:

List multiValues = {UNDEFINED}
if (Assoc.Items(myDefValues.(myAttrib)) != {})
multiValues = Assoc.Items(myDefValues.(myAttrib))
end

attrData.fData[categoryCounter].Values[1].(attrID).Values = multiValues //myDefValues.(myAttrib)

//attrData.fData[categoryCounter].Values[1].(attrID).Values = "" //{} //{""} //Assoc.CreateAssoc() //Assoc.CreateAssoc(Assoc.NotSetValue()) //all do not work
//attrData.fData[categoryCounter].Values[1].(attrID).Values = {UNDEFINED} //works fine ...