I’m using a formula to populate a listbox on a web app. Its a @DbColumn formula. Whenever I select one of the options and save, I go back into it, the options is no longer saved. All of the other data on the document is saving, so I know it must have to do with getting a handle on it when selected, but I’m not sure how to accomplish this. Help? Here is my formula.
res := @DbColumn(“” : “NoCache”;“”;“Goal Definitions”;3);
You imply that it is not being saved. Have you checked to see what value is saved in the field? Use the properties box in the client. I am betting that the save succeeds. tell us more.
I should have stated for you to check the properties from the view (checking properties from an open doc can show a totally different value).
From what I have read, this should work.
Is there any JavaScript on the form referencing this field? What is in the QuerySave and WebQuerySave events? Are other fields or form events referring to this field. Is the field computed? computed-when-composed? computed-for-display?
Ok, I was mistaken, and the value is being stored in the field, but not being displayed when opened from the web, but is being displayed when opened from the client. So, its a matter of actually not displaying vs not saving.
I wish that was the issue, but its not. I’ve tried making a duplicate field that shows when editable, and hiding the other field when read. Still does not display the choice from the web, even though it save sit in the document.
Ok, I’ve had to get creative to make this work with some hide-when formulas, but its now working. Geez, I had to go back to my App Dev 1 classes from 10 years ago to make something so simple work. Why I had to have multiple fields to do this on the web, I don’t know. thanks to all who provided input.