You’re offline. This is a read only version of the page.
5,124
I have a question on this page. I m thinking of changing the source type of Item List to TEMPORARY. The source table is Item. Since there are a lot of actions/nav/reports associated with this, I am just a little careful making the change. The reason I want to make it temporary is so I can populate a new column with calculated fields which need to be run real time. Creating a formfield column will not do as the logic requires more than summation, lookups or what have you. If I change to temporary, I gather I can modify the new column only without actually saving as it's not supposed to update the real table.
My question for you: do you see any repercussions when changing the source type of Item List Page to Temporary? Am I over simplifying the concept of changing to sourcetype to Temporary? My ultimate goal is to allow users to filter on the new column once I populate it at run time.
*This post is locked for comments
Hi All,
The calculated field that I have is not something that can be done via formfield or method simply because client wants to be able to filter that field as well. Anyway, I ended up creating a normal column fields and am updating these fields via a job every day. Thank you all for your answers.
If you change the table into a temporary then in real time you have to insert records back to table because temporary table does not hold any data and to populate data it will take considerable time (all will depend on how much recored you have).
There is no point of making table temporary. Create a list page and add your logic there.
You do not need to make it temporary to add a new column. You can create a new column in the page itself and then add your logic or calculation in the OnAfterGetRecord trigger of the page. By doing that for each record your logic will get executed.
NAV will only lock the tables (I would say SQL) when you do a modification or insert to a table or you purposely call for lock table function. So there won't be any performance issue for other users when you add a new column to Item list page.
As per my understanding you do not need to change it to temporary.
To add a new calculated field i don't think you need to change the list page source to temporary, create a new column in the page and use the source of it a function or variable which you can calculate in the onaftergetrecord of the page.
The calculated field does not have to updated it is just return value from a function which gets updated everytime you open the page.
If you use the source table as temporary then it will not have any records and you have to populate the temporary record anyway to show the values, so i don't think you need to change the source to temporary.
Hi mbr,
As the standard Item List doesn't allow you to modify anything (I mean the modifications happens only on the Item Card), I don't foresee any implication if you use a temporary table as the source for your item list. But you need to check how it's been used at other places (if you are using this Item List page explicitly based on your customization, if you have).
Best Regards,
MMV
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (