NetSuite has multiple customizations and there are multiple types of custom fields that can be created in an entity. Based on the field type the rules/actions from the NetSuite connector will change in the CIC rulesets. This information below demonstrates NetSuite SOAP Operations with different data types such as Multi-Select Custom Field, MultiselectSearchDouble, Multiselect Search Long, etc.
Pre-requisite
Create a custom field of type decimal number. Refer to https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N2828059.html for information about how to create a custom field.
CIC Implementation to Search for records based on the value in Double datatype custom field
Implementation has to be done in Search ruleset residing in the NetSuite Booster.
A method has to be created in the ruleset with SearchDoubleCustomField as the target.
- ID of the field needs to be mapped to ‘scriptId’.
- Required operator can be passed to ‘operator’ field. Values for operators can be found in https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4345782273.html
- The value that needs to be searched for should be mapped to ‘searchValue’.
The method created in the above step is called in createTransactionSearchAdvancedFromGenericFF method with List<SearchCustomField> customField being passed as the target.
When this Ruleset is executed, the NetSuite Search XML is formed to have the logic to look for the records containing the Double datatype field value as mapped in searchValue.
NetSuite Search XML:
Implementation of Get operation based on Double DataType custom field
Refer to the pre-requisite steps above to create a CustomField of Type Double in NetSuite.
CIC Implementation of Get operation based on the value in Double field
To map the value retrieved in Get response to a target field, implementation has to be done in the translation ruleset present inside the trading partner project.
The Ruleset uses NetSuite XML invoice as a source which is a response returned from NetSuiteGetBPS call.
- A method has to be created in the ruleset with DoubleCustomFieldRef as the source.
- Add a Move rule and map the field ‘value’ to the required output field or variable.
- Add a condition ‘StringEquals’ with sourceString1 as ‘scriptId’ from the schema and sourceString2 needs to be hardcoded with ID of the customField existing in NetSuite.
- The method created in the above step is called in mapInvoiceToN810EDI method with List<CustomFieldRef> customField.current being passed as the Source.
Implementation of Add operation for Double DataType custom field
Refer to the pre-requisite steps above to create a CustomField of Type Decimal Number in NetSuite.
CIC Implementation to map value to a custom field of type Double
Implementation needs to be done in the Translation Ruleset which resides in TP project.
- A method has to be created in the ruleset with DoubleCustomFieldRef as the target.
- In createSalesOrderFrom850EDI method, map the custom field ID to v_customReferenceScriptID and value to v_customReferenceValue variables.
- In the method created in step 1, map v_customReferenceScriptID to ‘scriptId’ and v_customReferenceValue to ‘value’.
Call the method in createSalesOrderFrom850EDI method with List<CustomFieldRef> customField.toTargetRef being passed as the target.
Implementation of Search operation based on Long DataType custom field
Pre-requisite:
Create a CustomField of Integer. Refer https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N2828059.html to understand how to create a custom field.
CIC Implementation to Search for records based on the value in Long datatype custom field
Implementation has to be done in the Search ruleset residing in the NetSuite booster.
- A method has to be created in the ruleset with SearchLongCustomField as the target.
- ID of the field needs to be mapped to ‘scriptId’.
- Required operator can be passed to ‘operator’ field. Values for operators can be found in https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4345782273.html
- The value that needs to be searched for should be mapped to ‘searchValue’.
The method created in the above step is called in createTransactionSearchAdvancedFromGenericFF method with List<SearchCustomField> customField being passed as the target.
When this ruleset is executed, the Netsuite Search XML is formed to have the logic to look for the records containing the Long datatype field value as mapped in searchValue.
NetSuite Search XML:
Implementation of Get operation based on Long DataType custom field
Refer to the pre-requisite steps above to create a CustomField of Type Long in NetSuite.
CIC Implementation of Get operation based on the value in Long field
To map the value retrieved in the Get response to a target field, implementation has to be done in the translation ruleset present inside the trading partner project.
The Ruleset uses NetSuite XML as a source which is a response returned from NetSuiteGetBPS call.
- A method has to be created in the ruleset with LongCustomFieldRef as the source.
- Add a Move rule and map the field ‘value’ to the required output field or variable.
- Add a condition ‘StringEquals’ with sourceString1 as ‘scriptId’ from schema and sourceString2 needs to be hardcoded with ID of the customField existing in Netsuite.
- The method created in the above step is called in the mapInvoiceToN810EDI method with List<CustomFieldRef> customField.current being passed as the Source.
Implementation of Add operation for Long DataType custom field
Refer to the pre-requisite steps above to create a CustomField of Type Integer in NetSuite.
CIC Implementation to map value to custom field of type Long
Implementation needs to be done in the Translation ruleset residing in the TP project.
- A method has to be created in the Ruleset with LongCustomFieldRef as the target.
- In createSalesOrderFrom850EDI method, map the custom field ID to v_customReferenceScriptID and value to v_customReferenceValue variables.
- In the method created in step 1, map v_customReferenceScriptID to ‘scriptId’ and v_customReferenceValue to ‘value’
- Call the method in createSalesOrderFrom850EDI method with List<CustomFieldRef> customField.toTargetRef being passed as the target.
Implementation of Search operation based on Date DataType custom field
Pre-requisite: Create a CustomField of Type Date.
Please refer to https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N2828059.html to understand how to create a custom field.
CIC Implementation to Search for records based on the value in Date datatype custom field
Implementation is to be done in the Search Ruleset residing in the NetSuite Booster.
- A method has to be created in the ruleset with SearchDateCustomField as the target.
- ID of the field needs to be mapped to ‘scriptId’.
- Required operator can be passed to ‘operator’ field. Values for operators can be found in https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4345782273.html
- The value that needs to be searched for, should be mapped to ‘searchValue’.
The method created in the above step is called in createTransactionSearchAdvancedFromGenericFF method with List<SearchCustomField> customField being passed as the target.
When this Ruleset is executed, the NetSuite Search XML is formed to have the logic to look for the records containing the Long datatype field value as mapped in searchValue.
NetSuite Search XML:
Implementation of Get operation based on Long DataType custom field
Refer to the pre-requisite steps above to create a CustomField of Type Long in NetSuite.
CIC Implementation of Get operation based on the value in Long field
To map the value retrieved in the Get response to a target field, implementation has to be done in the translation Ruleset that is in the trading partner project.
The Ruleset uses NetSuite XML as a source which is a response returned from NetSuiteGetBPS call.
- A method has to be created in the ruleset with LongCustomFieldRef as the source.
- Add a Move rule and map the field ‘value’ to the required output field or variable.
- Add a condition ‘StringEquals’ with sourceString1 as ‘scriptId’ from schema and sourceString2 needs to be hardcoded with the ID of the customField existing in Netsuite.
The method created in the above step is called in mapInvoiceToN810EDI method with List<CustomFieldRef> customField.current being passed as the Source.
Implementation of Add operation for Long DataType custom field
Refer to the pre-requisite steps above to create a CustomField of Type Integer in NetSuite.
CIC Implementation to map value to a custom field of type Long
Implementation needs to be done in the Translation ruleset residing in the TP project.
- A method has to be created in the ruleset with LongCustomFieldRef as the target.
- In createSalesOrderFrom850EDI method, map the custom field ID to v_customReferenceScriptID and value to v_customReferenceValue variables.
- In the method created in step 1, map v_customReferenceScriptID to ‘scriptId’ and v_customReferenceValue to ‘value’
- Call the method in createSalesOrderFrom850EDI method with List<CustomFieldRef> customField.toTargetRef being passed as the target.
Implementation of Search operation based on Date DataType custom field
Pre-requisite: Create a CustomField of Type Date. Refer https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N2828059.html to understand how to create a custom field.
CIC Implementation to Search for records based on the value in Date datatype custom field
Implementation has to be done in Search Ruleset residing in the NetSuite Booster.
A method has to be created in the ruleset with SearchDateCustomField as the target.
- ID of the field needs to be mapped to ‘scriptId’.
- Required operator can be passed to ‘operator’ field. Values for operators can be found in https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4345782273.html
- The value that needs to be searched for, should be mapped to ‘searchValue’.
- The method created in above step is called in createTransactionSearchAdvancedFromGenericFF method with List<SearchCustomField> customField being passed as the target
When this ruleset is executed, the Netsuite Search XML is formed to have the logic to look for the records containing the Double datatype field value as mapped in searchValue.
NetSuite Search XML:
Implementation of Get operation based on Date DataType custom field
Refer to pre-requisite steps above to create a CustomField of Type Date in NetSuite.
CIC Implementation of Get operation based on the value in Date field
To map the value retrieved in Get response to a target field, implementation has to be done in translation Ruleset present in the trading partner project.
The ruleset uses NetSuite XML invoice as a source which is a response returned from NetSuiteGetBPS call.
- A method has to be created in the ruleset with DateCustomFieldRef as the source.
- Add a Move rule and map the field ‘value’ to required output field or variable.
- Add a condition ‘StringEquals’ with sourceString1 as ‘scriptId’ from schema and sourceString2 needs to be hardcoded with ID of the customField existing in NetSuite.
The method created in the above step is called in mapInvoiceToN810EDI method with List<CustomFieldRef> customField.current being passed as the Source.
Implementation of Add operation for Double DataType custom field
Refer to the pre-requisite steps mentioned to create a CustomField of Type Decimal Number in NetSuite.
CIC Implementation to map value to a custom field of type Double
Implementation needs to be done in the Translation ruleset which is residing in TP project.
- A method has to be created in the ruleset with DoubleCustomFieldRef as the target.
- In createSalesOrderFrom850EDI method, map custom field ID to v_customReferenceScriptID and value to v_customReferenceValue variables.
- In the method created in step 1, map v_customReferenceScriptID to ‘scriptId’ and v_customReferenceValue to ‘value’.
- Call the method in createSalesOrderFrom850EDI method with List<CustomFieldRef> customField.toTargetRef being passed as the target.
Comments
0 comments
Please sign in to leave a comment.