Mexico UUID Plug-in Implementation Best Practices
This section provides best practices for developing Mexico UUID plug-in implementation.
-
The plug-in script file can have any name, as long as it contains an implementation of the interface function. See Create a Mexico UUID Plug-in Implementation Script File.
-
It is recommended that the UUID values of the transactions are stored in NetSuite. You can use a custom record type where the UUID values will be stored. For more information about creating custom record types, see Custom Records.
-
You can use SuiteScript API functions in a plug-in implementation. However, using these APIs may negatively affect the performance of the plug-in implementation. NetSuite recommends limiting the use of these APIs, where possible, to improve performance of the plug-in implementation. In general, searching for record yields better performance than loading NetSuite records.
Governance limits also apply to these functions, these add up to the usage limits of the Tax Audit Files scheduled script. For more information, see SuiteScript Governance and Limits.
Related Topics
- Tax Audit Files
- Mexico Tax Topics (Mexico Compliance SuiteApp)
- Mexico Electronic Accounting File (Mexico Compliance SuiteApp)
- Developing a Mexico UUID Plug-in Implementation
- Create a Mexico UUID Plug-in Implementation Script File
- Add the Mexico UUID Plug-in Implementation
- Enable the Mexico UUID Plug-in Implementation
- Test the Mexico UUID Plug-in Implementation
- Mexico UUID Plug-in Implementation Sample Code