How can I reproduce NetSuite’s native progress tracking (percentage) for a Map/Reduce script? In the standard NetSuite UI (e.g., when creating transactions in batch), the progress of background tasks is shown as a percentage that updates in real-time. I’d like to replicate this behavior for a custom Map/Reduce process — ideally showing the live progress percentage in a Suitelet. So far, I’ve tried using getPercentageComplete() in the Map/Reduce, but it seems to only return 0% or 100%. I’ve also looked into caching or custom records to track the execution progress manually. What’s the best practice to implement this kind of real-time progress feedback? Is there a recommended way to track and display the actual progress percentage of a running Map/Reduce, like NetSuite does internally?

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that tracking the progress of a Map/Reduce script in real-time, similar to NetSuite's native UI, can be a bit tricky. However, there are a few methods that you can try: 1. Use the Task ID: When your Suitelet starts the Map/Reduce script, keep hold of the task ID that was sent back. You can then ping the status of the Map/Reduce script every few seconds. This can be done by using a client script and JavaScript's

setTimeout

function. The status will tell you when it's complete, and you can use

N/cache

or a file to get the results. 2. Use a POST request in your Suitelet: You can have a POST request in your Suitelet using parameters to identify the call. The Suitelet can utilize the

N/Task

module to return the data back to the browser to show the progress. 3. Use a custom status page: You can create a custom status page for your script. There are examples available online, such as the one mentioned in the conversation: https://github.com/jeffreymkabot/netsuite-task-status. This page can display the status of the script using the standard NetSuite UI, allowing the user to see the completion percentage and know when the script has finished and if there are any errors. Remember, these methods might not work perfectly for all scenarios, and you might need to adjust them based on your specific requirements. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******