Export limit for xlsx. and csv

[sharley]

Export limit is 50K and total number of records present is only 29K. but when we export, we can only export upto 13K or 9K. does anyone know how to troubleshoot or why this is happening?

[Ankur Bawiskar]

@sharley 

Hope you are doing good.

Did my reply answer your question?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[yuvarajkate]

1. Query Timeout Limit

• Cause: ServiceNow enforces query timeouts to ensure system performance. If the export query takes too long, it might time out before fetching all records.
• Solution:
  • Check the glide.db.max_query_timeout property in the System Properties. Increase it if necessary, but be cautious as this affects all queries.
  • Refine the filter conditions to optimize the query.

2. Insufficient Permissions

• Cause: The user exporting the data might not have permission to view some records, even if they fall within the query scope.
• Solution:
  • Verify the user's roles and access permissions for the table and fields.
  • Check if Data Policies or ACLs are restricting access to certain records.

3. Export Method Limitations

• Cause: Different export methods have varying limits or behaviors. For instance:
  • List Export: Limited by the number of rows displayed or query performance.
  • Scheduled Data Export: More reliable for exporting large datasets.
• Solution:
  • Use the Export > Excel option only for smaller datasets.
  • For larger datasets, use Export > CSV or Export via Data Export API for better reliability.

4. Data Integrity Issues

• Cause: Corrupt or inconsistent records might cause the export process to fail mid-way.
• Solution:
  • Run a query to identify and validate records.
  • Check for any script errors or unusual characters in the data.

5. Record Chunking

• Cause: ServiceNow might chunk large queries, and some chunks may not process due to system load or query constraints.
• Solution:
  • Split the query into smaller chunks using conditions like sys_id ranges or date ranges.
  • Export each chunk individually and combine the results.

6. Browser or Session Limits

• Cause: Browser or session timeouts may interrupt the export process.
• Solution:
  • Use a robust client (like Postman or cURL) to query the data using the REST API.
  • Schedule the export job in System Definition > Export Sets for server-side processing.

7. Server Resource Constraints

• Cause: The ServiceNow instance might be under heavy load, affecting its ability to handle large exports.
• Solution:
  • Check system logs for signs of resource contention or errors.
  • Retry the export during off-peak hours.

 

 

Recommended Troubleshooting Steps

1. Verify the Filter: Ensure that your filter returns the correct set of records.
2. Test Smaller Batches: Try exporting smaller datasets (e.g., 5,000 or 10,000 records) to see if the issue persists.
3. Check Logs: Review the System Logs > All for errors during the export process.
4. Use Export Sets: Navigate to System Definition > Export Sets for a more controlled and scalable export method.
5. Contact ServiceNow Support: If the issue persists after all troubleshooting, it could be due to instance-specific constraints or bugs. Opening a case with ServiceNow support is advisable.

[Runjay Patel]

Hi @sharley ,

You can increase and decrease the limit while updating the property.

-------------------------------------------------------------------------

If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.

Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay

-------------------------------------------------------------------------

[vishwajeet5550]

Use Scheduled Export if the export is too large to be done interactively. Scheduled exports allow for larger data sets to be processed without hitting timeout errors.