[Michael Yarbrough]

So, in my testing this seems to work:

setFieldValue("Level_x0020_3_x0020_Org", "NORTH FLORIDA,WEST FLORIDA", false);

However, it appends instead of replaces the existing values. Is there an documentation on the options and usage of setFieldValue?

Getting close!

[Michael Yarbrough]

We may be able to get the latest version and test. Just to be sure I am testing correctly, if I do this I should be able to set it and see the new values before a save, correct?

In the development console. North Florida and West Florida are valid values in my lookup list:

setFieldValue("Level_x0020_3_x0020_Org", ["NORTH FLORIDA", "WEST FLORIDA"]);
console.log(JSON.stringify(getFieldValue("Level_x0020_3_x0020_Org")));

[Michael Yarbrough]

We are on 1.255. I have tried setting the ids instead of the names of the lookup values as well but that does not work either. I am able to update the lookup fields through a REST call, which will work, except that when the save on the form is called I get a conflict error stating someone has made changes to the form since it was last opened.

[Michael Yarbrough]

Tried this to no avail:

setFieldValue("Level_x0020_3_x0020_Org", ["GR PA", "SOUTH FLORIDA"]);
console.log(JSON.stringify(getFieldValue("Level_x0020_3_x0020_Org")));

The getFieldValue still shows the original values, not the ones I am trying to set.

[Michael Yarbrough]

Using SP 2013. I believe that is what I am doing, however, it doesn’t seem to be taking. I am thinking that I need to use Id’s of the options instead of the string names since it is a lookup, and perform a setFieldValue on the hidden Id column, like `setFieldValue(“MultiLookupId”,[“1″,”2”]);

Thoughts?

[Author]

Posts