Is there any way to find the record type numerical...
# suitescriptm
Madelene Sköld
08/09/2023, 9:17 AMIs there any way to find the record type numerical id based on the record type name id, and the other way around, like “account <--> -112”?
n
NElliott
08/09/2023, 9:53 AMAre you asking for the internal id of a custom record? (i.e. the definition of it not an instance of the custom record)
NElliott
08/09/2023, 9:56 AMI suspect you mean the standard NS records since you gave "account" as an example.
b
battk
08/09/2023, 10:12 AMits more common when using suitetalk, where you basically use a lookup on the Internal IDs for NetSuite Record Types
battk
08/09/2023, 10:16 AMif you wanted it to be dynamic, then 2.3.5 Transient Record Controller from the SAFE guide can work for numbers to ids
w
Watz
08/09/2023, 11:26 AM@battk OT, Based on the Transient Record Controller example, wouldn't be faster to use a SuiteQL nowadays? The document is dated 2022 but this part is probably older then that.
b
battk
08/09/2023, 11:49 AMthere are 2 tables relating to record types, one is actual Record Types, the other is Scripted Record Types, they have different ids
battk
08/09/2023, 11:49 AMworkbook data source has both tables, but no relation between them
battk
08/09/2023, 11:51 AM@Madelene Sköld requires a relation between the two tables, the id
account-112battk
08/09/2023, 11:52 AMthats where you can use the transient record controller, which uses field sourcing, where there is actually a relationship between the two tables/lists
m
Madelene Sköld
08/10/2023, 7:30 AMExactly, so the relation between the internal ids and the references of different record types, not instances of the records themselves. My colleague just found two tables that seem to be possible to query through SuiteQL to retrieve this relation, joining the “name” columns, but there is no documented join between the tables so we were wondering if you can possibly see a situation where the name in one doesn’t match the name in the second? The tables are ScriptRecordType and ScriptCustomRecordType, and an example of the query for account would be
Copy code
select * from ScriptRecordType
join ScriptCustomRecordType
on ScriptRecordType.name = ScriptCustomRecordType.name
where ScriptRecordType.skey = upper('account')Madelene Sköld
08/10/2023, 7:33 AMI tried the transient record controller option (great tip in general by the way, thanks!) and I was able to retrieve the internal id with “RECORD” prepended, so in this case, I got “RECORD-112". Since removing the RECORD part of it is easily done, this is definitely an option as well!
b
battk
08/10/2023, 9:06 AMdepends on how good a solution you need, nothing is preventing a custom record from being named the same as a standard record
battk
08/10/2023, 9:06 AMor even a standard record being renamed the same as anothe record
battk
08/10/2023, 9:21 AMits also possible for 2 custom records to have the same name via translations, but thats extra unlikely unless someone is trying to cause a failure
battk
08/10/2023, 9:29 AMfor the transient record controller, you are looking at the wrong field if you are getting Record-112, you should be looking at the List/Record field instead
battk
08/10/2023, 10:00 AMyou will also want to double check how transaction, entities, and items share record types
battk
08/10/2023, 10:02 AMfor example, a sales order scripted record type doesnt have a matching sales order record type
battk
08/10/2023, 10:02 AMthere is only a shared transaction record type
m
Madelene Sköld
08/10/2023, 1:49 PMI discovered the issue with items, transactions etc as well, so I think I’ll have to go about this issue a whole nother way… But thank you for the input and the indirect confirmation that this is messy and best to stay away from if possible
16 Views