I just noticed that *LIST* objects do not have the...
# sdfs
stalbert
04/06/2021, 3:10 PMI just noticed that LIST objects do not have their (numeric) internal ids in the xml. Is there a way to specify the internal ids so that I can be sure a list matches id-by-id when deploying to another account?
stalbert
04/06/2021, 3:18 PMthis seems a rather glaring oversight, given that we use numeric ids for list values in SuiteScript. I have a situation where I have a list with ids like 1,2,3,5. I'm pretty sure when I deploy to prod that will become 1.2.3.4 and break any script that referred to value 5 for that last list item?
w
Watz
04/06/2021, 3:42 PMYou can't set the internal ids for lists (or anything). I usually write a function to translate the scriptids to the internalid on execution using a search on the list. You could also use N/cache if this is fetched often in multiple executions.
s
stalbert
04/06/2021, 5:00 PMegads
stalbert
04/06/2021, 5:19 PMI definitely don't want to incur the complexity or resource hit of doing a search for these immutable values.
stalbert
04/06/2021, 5:19 PMbut I can understand you doing so as a way to compensate .
w
Watz
04/06/2021, 6:07 PMHere's a write-up regarding the issue https://netsuite.smash-ict.com/2020/09/learn-to-write-custom-list-code-that-works-across-environments/
👍 1
s
stalbert
04/07/2021, 8:48 PMI've read before and for these essentially static lists the runtime burden of doing a list search and the additional complexity is unacceptable
w
Watz
04/07/2021, 10:28 PMCan't argue there. I would have liked it to be possible to refer to the records using scriptId.
Since you cannot have installation scripts in sdf (I think), how about you programmatically edit a lib-file on the first run with the current environments ids?
s
stalbert
04/07/2021, 11:18 PMthese are all reasonable ideas if buiding a suiteapp In my case the only time this has been an issue is when working with an existing list that needs to change on both SB/prod for a given client.
stalbert
04/07/2021, 11:19 PMI generally work on customizations not suiteapps. This issue makes me a bit thankful i'm not working on a suiteapp to be used on many accounts!
2 Views