Here are some observations on server-side table fields (SSTFs) that may help you understand how to use them.
Speaking in general terms, there are comparatively few use cases where developers need to use SSTFs. Many of the use cases that are satisfied by using SSTFs can also be satisfied using other techniques such as Push Fields or Direct SQL. So if you have no immediate plan to use an SSTF, then don't worry about the comment in the documentation. Specifically about the documentation's comment, as I understand it the intent is to state that if an SSTF has a row, and a developer modifies the contents of that row, then the modification is not reflected in the foreign table which is the source of data for the row. If a developer's intent is to update the data in the foreign table, then it will be necessary to use workflow to update the data and then optionally refresh the table field to reflect the update. Many of the experienced developers here on ARSList have built solutions using SSTFs, so my advice would be to wait until you have a requirement that may be satisfied by using an SSTF and then ask your questions. HTH, --Phil ________________________________________ From: Action Request System discussion list(ARSList) [[email protected]] On Behalf Of Sweety [[email protected]] Sent: Monday, May 19, 2014 18:04 To: [email protected] Subject: Re: Data in server-side table fields is read-only. I have not said that I want to create a table field at all. It says data is read only. Why I cannot update the data in server side table? I do not understant the statement "Data in server-side table fields is read-only". Make me understand it please. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
