Document Variable Name Is Added Before Attributes in Commerce Attribute Sets
Last updated on JANUARY 02, 2018
Applies to:Oracle BigMachines CPQ Cloud Service - Version 2016 R1 and later
Information in this document applies to any platform.
In commerce attribute sets such as"Customer Attribute", "Invoice To Attributes", "Ship To Attribute", "Sold To Attributes", and "eSignature Attributes", the document variable name is added before the attributes when adding them into functions.
Steps to reproduce:
- Create a Attribute set in commerce. For example "eSignature Attributes" set.
- Check the variable name of the attributes in this attribute set. For example, if you have an attribute "eSignature File Attachment[eSignature]" in this set, this attribute will have a variable name of "_eSignature_esig_file_attachment".
- Open any library function or advanced modification function in an action.
- If adding this attribute to the function, the attribute variable name is "_quote_process_eSignature_esig_file_attachment" or "_transaction_eSignature_esig_file_attachment". The prefix depends on the variable name of the quote document for the commerce process.
When the function runs on the quote, the following error may be observed:
Attribute XXXX cannot be found
This is because the variable names in the function and on the quote do not match.
This issue started to occur since 2016 R1.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms