Please use docs.servicenow.com for the latest documentation.

This site is for reference purposes only and may not be accurate for the latest ServiceNow version

Talk:Exporting Data

From Wiki Archive
Jump to: navigation, search

Contents

2.3 Breaking Up Large Exports (syntax error) -- Sean.jacobs 23:28, 10 April 2012 (UTC)

Hey, the lines:

The following example shows a query that uses a sys_id of b4aedb520a0a0b1001af10e278657d27. Use the syntax shown in this query to export the next chunk of records.

https://demo.service-now.com/glide/syslog_list.do?sysparm_query=sys_id%3Eb4aedb520a0a0b1001af10e278657d27sysparm_order=sys_id&XML


Should be:

The following example shows a query that uses a sys_id of b4aedb520a0a0b1001af10e278657d27. Use the syntax shown in this query to export the next chunk of records.

https://demo.service-now.com/glide/syslog_list.do?sysparm_query=sys_id%3Eb4aedb520a0a0b1001af10e278657d27%26sysparm_order=sys_id&XML

Re: 2.3 Breaking Up Large Exports (syntax error) -- Sean.jacobs 23:43, 10 April 2012 (UTC)

Also, that won't give you the record with a sys_id of b4aedb520a0a0b1001af10e278657d27 (which is the 50, 001st record according to the previous steps). You need to use:
https://demo.service-now.com/glide/syslog_list.do?sysparm_query=sys_id%3E%3Db4aedb520a0a0b1001af10e278657d27%26sysparm_order=sys_id&XML
Though it may be better to copy the sys_id of the 50,000 record and stick with sys_id>{value}

Re: Re: 2.3 Breaking Up Large Exports (syntax error) -- Vaughn.romero 23:56, 17 April 2012 (UTC)

Thank you for your suggestion. See the section Breaking Up Large Exports for the updated sample URL query.

Re: 2.3 Breaking Up Large Exports (syntax error) -- Geoff (talk) 10:52, 10 June 2014 (PDT)

According to Julio Fernandez (NOW), the syntax is sysparm_orderby (not sysparm_order). See INT2378311.

Help for new users -- Gflewis 13:39, 11 May 2012 (UTC) -- Gflewis 13:39, 11 May 2012 (UTC)

For the benefit of new users, can you please add a screenshot showing how to right click on the title bar. Thanks.

Re: Help for new users -- Gflewis 13:39, 11 May 2012 (UTC) -- Vaughn.romero 18:31, 14 May 2012 (UTC)

Thank you for the suggestion. See the section Exporting from Lists for a screenshot illustrating how to export a list with right-click functionality.

Adding sys_id to List View -- Chasingtheflow (talk) 10:05, 12 December 2013 (PST)

The article suggests adding sys_id to a list view as though this is trivial. Though that option isn't typically available through the list view editor. What is the preferred method for adding sys_id to the list view?

Re: Adding sys_id to List View -- Vaughn.romero (talk) 10:44, 12 December 2013 (PST)

Thank you for your feedback. I've updated the section Breaking Up Large Exports to use instructions other than adding the Sys ID to the list since this is not a valid option.

Section 8.2 uses two different "sysparm_order" parameters -- Rickseiden (talk) 08:18, 1 January 2014 (PST)

It appears that in step 3 of 8.2 it says we should use "sysparm_order", but in step 6 it says we should use "sysparm_orderby"

Re: Section 8.2 uses two different "sysparm_order" parameters -- Vaughn.romero (talk) 09:05, 6 January 2014 (PST)

Thank you for your feedback. The reason we are using two different sysparm parameters is that one parameter can only sort lists in the UI (sysparm_order) and the other parameter can only sort lists during an export (sysparm_orderby) (see URL Query parameters for more information). In step 3 we are determining the Sys ID of the next record but not actually exporting it. Since this is only an action from the UI, we use the sysparm_order parameter. In step 6 we need to actually export records so we have to use the sysparm_orderby parameter. This is a potential area of improvement in the product as ideally there would only be one parameter that sorted both lists in the UI and lists during export.

Section 3.1 "sysparm_default_exported_fields" parameter -- Satoshi.yamamura (talk) 16:29, 19 February 2014 (PST)

We should use "sysparm_default_export_fields" instead of "exported" which is typo. Also, this parameter works only on Dublin. I'd appreciate if you would correct the parameter and add the note about available version. Thanks.

sysparm_order no longer works in Dublin, must use ORDERBY -- Geoff (talk) 12:42, 29 May 2014 (PDT)

We have found that queries containing "sysparm_order=sys_id" are no longer sorted properly in the Dublin release. We have had to change all such queries to use "^ORDERBYsys_id" instead.

Re: sysparm_order no longer works in Dublin, must use ORDERBY -- Haninger.3 (talk) 19:27, 29 May 2014 (PDT)

This could be a problem in Calgary as well, or it's possible I don't know what I'm doing. I tried to follow the steps for breaking up an export of data, but I would get lots of "overlap" between the exports. For exporting large tables (like sc_req_item and incident which - for us - have >200,000 rows each) I've found that it's best to skip trying to sort and query by the sys_id and instead just query by the incident or request item number. For example: https://demo.service-now.com/incident_list.do?CSV&sysparm_query=number%3EINC1234567&sysparm_record_count=50000

When querying and sorting by the sys_id, I'd get two files with 50,000 records each, but there was about 50% "overlap" between the two, as though I would get incidents 1-50,000 in the first export and 25,000 to 75,000 in the second and so on.

Re: Re: sysparm_order no longer works in Dublin, must use ORDERBY -- Ludwig.adriaansen (talk) 05:12, 2 June 2014 (PDT)

Thank you for your feedback. We will investigate and get back to you.

Re: sysparm_order no longer works in Dublin, must use ORDERBY -- Joseph.messerschmidt (talk) 13:46, 24 July 2014 (PDT)

Thanks for alerting us to this. I've replaced the outdated information. The ORDERBY operator is correct. I was not able to sort exported records using any of the possible operators in the Calgary release. I will confirm if this is new behavior that was added with Dublin.

export as pdf form -- Gerrit.kuilder (talk) 09:53, 11 March 2015 (PDT)

"Note: When exporting PDF data from a form, only the fields that are visible from the current view are exported. When exporting XML data, however, all the fields are exported, regardless of the view. CSV and Excel records cannot be exported from a form."

relevant incident INT2539705 could details be added that although UI policies can hide fields from a view it will still export those fields in the pdf

Re: export as pdf form -- Joseph.messerschmidt (talk) 10:03, 11 March 2015 (PDT)

Thanks for the feedback Gerrit. I've updated the note to correctly indicate that fields hidden by UI policy are included in the PDF.

Column Headers -- SNFan (talk) 08:17, 8 May 2015 (PDT)

is it worth noting that the column headers exported are different depending on whether you choose Excel or CSV? If you use CSV you get DB field names vs Labels in Excel

Re: Column Headers -- Julie.phaviseth (talk) 16:10, 8 May 2015 (PDT)

Thank you for your feedback. I forwarded your question to the writer.