Troubleshooting Mobile Issues Using Developer Tools in NetSuite

The details below provide guidance on troubleshooting mobile issues in NetSuite using Chrome Developer Tools, which is instrumental for developers and administrators when diagnosing connectivity errors and data loading failures.

How Can Developer Tools Help Troubleshoot Mobile Issues?

You can utilize developer tools to diagnose mobile issues while running the mobile app in the Chrome browser. Other browsers like Firefox and Safari offer similar functionalities, enabling a cross-browser approach to debugging.

Steps to Check Mobile Issues Using Chrome Developer Tools:

1. Open Developer Tools: Right-click on the mobile app page and select Inspect.
2. Access the Network Tab: A panel opens on the right; click on the Network tab.
3. Filter Mobile Requests: Since mobile requests begin with "scriptlets," click the Fetch/XHR button and type suitelet in the Filter field.
4. Refresh the Mobile Page: This action triggers the capture of network requests.

You should examine both inventory and event requests to confirm that the data loads correctly. For specific jobs, focus on inspecting the resource request to validate tab data. Submitting a tab should lead to inspecting payloads and responses for any errors or confirmation of success.

Common Issues and Best Practices

Here are several effective strategies to address frequent mobile issues:

• Empty Dropdowns: If dropdowns appear blank, inspect the inventory request for any errors or missing data.
• Jobs Not Loading: Check the event request to identify errors or confirm if results are not available.
• Tab Load Failures: For any malfunctioning mobile tab, inspect the resource request related to that job and tab.
• Data Saving Issues: Review the payload and response when data saving encounters problems to catch error details.
• Testing Configuration Changes: Always test configuration modifications within your sandbox account prior to implementing them in your production environment.
• Document Customizations: Keep detailed records of any overrides and customizations made to facilitate reverting changes if required.
• Use Configuration Preview: Leverage the Configuration Preview feature to observe the complete, merged configuration and aid in debugging.
• Backup Core Config: Before introducing changes, copy the full array object from the core configuration to ensure a fallback is available.

These practices will help streamline your troubleshooting process and improve the overall experience for users on mobile devices.