it depends what you're trying to do with the record and how unscriptable it is. E.g. many records may be unscriptable in client-side but still available server side, or not available for UEs but can be access via scheduled scripts.

wow, I was unaware of that second part of your statement (available to scheduled but not UE?)

The part I'm trying to automate is Wave creation. Waves are partially scriptable, for read and update, but do not support create. They are also unavailable for mass update, csv import, and workflows.

@stalbert yeah we ran into it with ARM records - they are technically "server-side scriptable" but there's a note on the script supported records page that user event scripts are not supported, so only scheduled/M/R would work

interesting. Is there a specific record type for which you saw that behavior? e.g. RevenueArrangement, RevenueElement, etc?

this is what is designated in the supported records page, and we experienced it specifically with rev rec plans

By 'not supported in userevent scripts' I assume they mean you can't attach a UE script to those record types... not that you can't otherwise manipulate them in a UE attached to some other record type?

ah yes, that's my understanding as well - you can't deploy a UE to them, not that they can't be touched at all serverside UE

"script supported records page" is this the record browser?

nah, it's a help/suiteanswer page, if you search "suitescript supported records" in help or suiteanswers, there's an article with a big table of all record types and the record ID, scripting level, and whether it's scriptable client or server-side.