Hey everyone, has anyone ever “renamed” their cust...
# generalr
Ryan Longenecker
08/12/2021, 10:19 PMHey everyone, has anyone ever “renamed” their customer record and it caused issues with their scripts not finding the customer records anymore?
s
Shubi
08/13/2021, 12:15 AMNo - renaming would never cause issues like that because if you're scripting on customer, you're still using the internalid of the record. It could be a potential defect unless something else is causing it. I'm a NetSuite Solutions Architect, feel free to reach out if you need help.
c
CD
08/13/2021, 9:36 AM@Shubi I don't think he means renaming an actual Customer. He means renaming the Customer record itself (to eg: Client)
s
Shubi
08/13/2021, 1:16 PM@CD I know what he meant but renaming won't change the internal id of the record. It will always remain "customer".
r
Ryan Longenecker
08/13/2021, 4:30 PMHey @Shubi @CD we have a script giving an error. The custom record is renamed and it’s stating this as the issue. It can’t find “newrecordname”. Is it possible “customer” was used in the script but can’t find it due to the renaming?
s
Shubi
08/13/2021, 4:31 PMAre you able to share the script?
r
Ryan Longenecker
08/13/2021, 4:33 PMThis is the error: “”type”:“internal error”,“code”“INVALID RCRD TYPE”,“details”“The record type [MEMBER] is invalid.“,”
Ryan Longenecker
08/13/2021, 4:33 PMCustomer was renamed to MEMBER
s
Shubi
08/13/2021, 4:33 PMyeah that is the problem
Shubi
08/13/2021, 4:34 PMchange MEMBER to CUSTOMER
Shubi
08/13/2021, 4:34 PMrenaming only works visually but the record type internal id will always remain Customer
r
Ryan Longenecker
08/13/2021, 4:35 PMCan’t change the customer naming back to customer. Needs to stay member
Ryan Longenecker
08/13/2021, 4:35 PMgetEntityType returns the renamed customer record type/name. It is not recognized by the url.resolveRecord method, which is looking for the standard record type value.
s
Shubi
08/13/2021, 4:35 PMlets connect.
r
Ryan Longenecker
08/13/2021, 4:36 PMI can’t change the script, just wanting to confirm this is possible to happen with renaming the records
c
CD
08/13/2021, 4:37 PMOh, are you trying to get it dynamically because of Leads/Prospects?
r
Ryan Longenecker
08/13/2021, 4:37 PMThis is the script that is causing the issue:
Ryan Longenecker
08/13/2021, 4:37 PMfunction getEntityType(id) {
2 return search.lookupFields({
3 type: ‘entity’,
4 id: id,
5 columns: [‘type’]
6 }).type[0].text;
7 }
Ryan Longenecker
08/13/2021, 4:38 PM“Member” isn’t found. It’s looking for customer
s
Shubi
08/13/2021, 4:38 PMI see.. and the script is deployed on how many record types?
r
Ryan Longenecker
08/13/2021, 4:38 PMMultiple
s
Shubi
08/13/2021, 4:40 PMnot a great solution but add a custom field on these entity record types with formula {type} to get the actual entity type:
• MEMBER: Customer
• Employee:Employee
And pass that as type
r
Ryan Longenecker
08/13/2021, 4:41 PMOk, thank you! Just to confirm, this script is erroring because the record was renamed?
s
Shubi
08/13/2021, 4:42 PMI still don't think so. even though customer, employee, leads, prospects are entities, it needs the actual record type id
r
Ryan Longenecker
08/13/2021, 4:43 PMSo since it’s renamed to member, the record type of member isn’t found?
s
Shubi
08/13/2021, 4:51 PMYou can rename it to whatever you want but the id will always be "customer".
Shubi
08/13/2021, 4:51 PMmessage has been deleted
Shubi
08/13/2021, 4:51 PMrenaming it won't affect the backend and you cannot manipulate the record browser
Shubi
08/13/2021, 4:52 PMI can help you with the script if you want. Feel free to reach out
r
Ryan Longenecker
08/13/2021, 5:23 PMHey @Shubi thanks for sending this over. I can’t change the scripts, only our devs can. I am trying to see if the issue is in renaming the record to member. Seems like it shouldn’t error out but still is due to the renaming. Any ideas of why?
s
Shubi
08/13/2021, 5:36 PMSending you a dm
b
battk
08/13/2021, 9:45 PMthe guess here is that something is using getEntityType as the recordtype
battk
08/13/2021, 9:46 PMwhich is wrong, there is an actual recordtype that should be used instead
2 Views