Is there additional value to the Script IDs you ca...
# suitescript
e
Is there additional value to the Script IDs you can set on custom list entries? It doesn't seem like you can use that as the key for
setValue()
. Is it just there so you can run a search on the custom list to find the right internal ID?
I haven't found any other way to use them.
Maybe you have already read the post from your podcast guest 🙂
e
Right, so just there for a search key
Thanks though I had not read it
w
afaik
e
When trying to set it directly via console, it looks like it tries to do some sort of lookup, but fails
With an Unexpected Error, which is all the further I'm willing to investigate right now 😄
w
I don't recall Chidi using N/cache, but that would probably be a good idea if you do these list-lookup often
s
Yeah it's (lack of) usefulness is pretty similar to externalid
e
^ That's the immediate parallel I drew as well
It's like almost super useful
s
externalid does have the useful property of guaranteed uniqueness IIRC
I also disagree that the solution presented in that article (forcing a search) is universally 'better' than the other two.
d
Wouldn't this be used by SDF to identify your product's data, still allowing for custom entries?
s
I was thinking the same thing (if I understand you correctly), that those scriptids are important for uniqueness across NS accounts. Or so they can be referenced perhaps (via searches like in that article) for things like post install scripts.
I presume that NS stores all custom lists in a single table.
e
I was hoping to be able to leverage that uniqueness in scripts without needing to search, but it would seem that is not possible.
d
I'm with Eric. There are so many very useful features that are just out of reach with scriptid and externalid. Like Upserts and Loads without searches
Now, if the externalid was 'also' namespaced ... look out!
z
The solution in that article is nice. It could be improved by the use of N/cache. Cache would approach the speed you get with a hard-coded IDs in the hash/enum object. Cache would also help reduce governance usage and avoid hard-coded scriptid/internalid values.