Forum Discussion
I’ve handled something like this before by manually (one time) encrypting the values using an Encrypt Field snap using a Passphrase-based Account. Then hardcoded those encrypted values in a mapper like you mentioned, with a Decrypt Field snap after it using the same Passphrase-based Account, to decrypt the values and use them at runtime.
Thanks, Supratim I updated the WSDL year value to 2023 and yes now the object is displayed as a Standard object. However, the actual issue persists in retrieving data for a NetSuite object by passing the object name and some other field ($record.entity.internalId) of the same object as input parameters.
Related Content
- 2 years ago