This function runs an existing report, using its report_id, which can be obtained from the get_reports function.<\/p>\n
http:\/\/www.myserver.com\/evj\/ExtraView\/ev_api.action? This function runs an existing report, using its report_id, which can be obtained from the get_reports function. SYNTAX http:\/\/www.myserver.com\/evj\/ExtraView\/ev_api.action? user_id=username &password=password\u00a0OR\u00a0[&access_token=token-value] &statevar=run_report [&username_display=ID | LAST | FIRST] [&api_reverse_lookup=NO | YES] &report_id=nnnn &page_length=100 &record_start=1 &record_count=120 \u200b[&p_output_type=MS_EXCEL | MS_WORD | PDF | TEXT] [&persist_handle=xxx] [&exclude_data_images=no | yes] [&field1=value1] [&field2=value2] [&fieldn=valuen] NOTES This command runs a report from…<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":24223,"menu_order":68,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_lmt_disableupdate":"no","_lmt_disable":"","_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"class_list":["post-24266","page","type-page","status-publish","hentry"],"acf":[],"yoast_head":"\n
\nuser_id=username
\n&password=password<\/span>\u00a0OR\u00a0[&access_token=token-value]
\n&statevar=run_report
\n[&username_display=ID | LAST | FIRST]
\n[&api_reverse_lookup=NO | YES]
\n&report_id=nnnn
\n&page_length=100
\n&record_start=1
\n&record_count=120 \u200b[&p_output_type=MS_EXCEL | MS_WORD | PDF | TEXT]
\n[&persist_handle=xxx] [&exclude_data_images=no | yes]
\n[&field1=value1] [&field2=value2] [&fieldn=valuen]<\/span><\/p>\nNOTES<\/h3>\n
\n
p_output_type\u00a0<\/code>parameter.\u00a0 You may output the report to Microsoft Excel, Microsoft Word, Adobe PDF or text.\u00a0 If the parameter is not provided, the report will output to XML<\/li>\n\n
field1=value1<\/code>\u00a0and\u00a0field2=value2<\/code>\u00a0provide runtime filters that are required by the report. For a name value pair to be valid with this API call, the field must have been defined within the report as a runtime filter. You must provide a name value pair for each and every runtime filter in the report you are running. Failure to do this will result in an error being displayed.\u00a0 More sophisticated runtime filters may be defined as follows in the following example.\u00a0 This defines 3 runtime filters, each predefined in the report editor within the desktop user interface:\n\n
\n
DATE_CREATED<\/code>\u00a0– Date Created<\/li>\nTIMESTAMP\u00a0<\/code>– Last Modified<\/li>\nPRIORITY\u00a0<\/code>– Priority<\/li>\n<\/ul>\n<\/li>\n
\nuser_id=xx&password=xx
\n&statevar=run_report
\n&page_length=100
\n&record_start=1
\n&username_display=LAST
\n&report_id=1234
\n&api_reverse_lookup=YES
\n&p_ql_search_mode=ADVANCED
\n&p_fset=0
\n&p_fieldName=DATE_CREATED
\n&p_operator=between
\n&p_value1_EVDISPLAY=09\/01\/2017
\n&p_mvalue1=09\/01\/2017
\n&p_value2=09\/30\/2017
\n&p_fset=0
\n&p_fieldName=TIMESTAMP
\n&p_operator=>
\n&p_value1_EVDISPLAY=09\/08\/2017
\n&p_mvalue1=09\/08\/2017
\n&p_fset=0
\n&p_fieldName=PRIORITY
\n&p_operator==
\n&p_value1_EVDISPLAY=P 2
\n&p_mvalue1=<\/code><\/li>\n
\n1.\u00a0p_fset<\/code>
\n2.\u00a0p_fieldName<\/code>
\n3.\u00a0p_operator<\/code>
\n4.\u00a0p_value1_EVDISPLAY<\/code>
\n5.\u00a0p_mvalue1<\/code>
\n6.\u00a0p_value2<\/code><\/li>\n
\n1.\u00a0p_fset<\/code>\u00a0–\u00a0p_fset<\/code>\u00a0is always set to\u00a00<\/code>, like\u00a0p_fset=0<\/code>
\n2.\u00a0p_fieldName<\/code>\u00a0–\u00a0p_fieldName<\/code>\u00a0is the Data Dictionary name, such as\u00a0p_fieldName=DATE_CREATED<\/code>,\u00a0p_fieldName=TIMESTAMP<\/code>, and\u00a0p_fieldName=PRIORITY<\/code>
\n3.\u00a0p_operator<\/code>\u00a0–\u00a0p_operator\u00a0<\/code>is one of the following values but depends on the display type of the field, the same as in the desktop user interface
\n\u00a0\u00a0\u00a0\u00a0\u00a0 =<\/code>
\n\u00a0\u00a0\u00a0\u00a0\u00a0 ><\/code>
\n\u00a0\u00a0\u00a0\u00a0\u00a0 <<\/code>
\n\u00a0\u00a0\u00a0\u00a0\u00a0 <><\/code>
\n\u00a0\u00a0\u00a0\u00a0\u00a0 <=<\/code>
\n\u00a0\u00a0\u00a0\u00a0\u00a0 >=<\/code>
\n\u00a0\u00a0\u00a0\u00a0\u00a0 contains<\/code>
\n\u00a0\u00a0\u00a0\u00a0\u00a0 not_empty<\/code>
\n\u00a0\u00a0\u00a0\u00a0\u00a0 empty<\/code>
\n\u00a0\u00a0\u00a0\u00a0\u00a0 between<\/code>
\n4.\u00a0p_value1_EVDISPLAY<\/code>\u00a0– for\u00a0POPUP<\/code>,\u00a0DATE\u00a0<\/code>and\u00a0DAY\u00a0<\/code>display type fields, you need to specify this value
\nFor\u00a0DATE\u00a0<\/code>and\u00a0DAY\u00a0<\/code>fields,\u00a0 an example is\u00a0p_value1_EVDISPLAY=09\/08\/2017<\/code>
\nFor\u00a0POPUP\u00a0<\/code>fields an example is\u00a0p_value1_EVDISPLAY=P 2<\/code>
\nNote: you need to have the parameter\u00a0api_reverse_lookup=YES\u00a0<\/code>to enable the reverse lookup of list fields using their title rather than their name or the database UDF_LIST_ID.
\n5.\u00a0p_mvalue1<\/code>\u00a0– All display types, except\u00a0POPUP<\/code>\u00a0need to specify the database values
\nFor\u00a0DATE\u00a0<\/code>and\u00a0DAY<\/code>\u00a0fields, you need to specify the same value of\u00a0p_value1_EVDISPLAY<\/code>, for example\u00a0p_mvalue1=09\/08\/2017<\/code>
\nFor\u00a0POPUP<\/code>\u00a0fields, you don’t need to specify any parameter if\u00a0api_reverse_lookup=YES<\/code>
\nFor other display types, you need to specify the database values
\n6.\u00a0p_value2<\/code>\u00a0–\u00a0p_value2<\/code>\u00a0is only used for\u00a0DATE\u00a0<\/code>and\u00a0DAY\u00a0<\/code>fields when you using the\u00a0between<\/code>\u00a0operator, for example\u00a0p_value2=09\/30\/2017<\/code><\/li>\n<\/ul>\n<\/li>\naccess_token<\/code>\u00a0parameter allows you to use a valid OAuth2 token obtained with the\u00a0get_token<\/code>\u00a0command.\u00a0 If you provide the\u00a0access_token<\/code>\u00a0parameter, then the\u00a0user_id<\/code>\u00a0and\u00a0password<\/code>\u00a0parameters should not be provided.\u00a0 This prevents the password being sent in clear text over your network connection<\/li>\nsearch\u00a0<\/code>API command.\u00a0 The\u00a0search\u00a0<\/code>API command has more flexibility in this case<\/li>\nexclude_data_images<\/code>\u00a0will inhibit images embedded within HTML Area fields from being output, if set to a value of\u00a0yes<\/code><\/li>\np_ql_search_mode=ADVANCED<\/code>, you must use the Advanced filters format in the run_report<\/code> command. For example, if you have a hierarchy report with runtime filters such as:parent level STATUS = ask at runtime
child level STATUS = ask at runtime
<\/code> and you want parent level status = Open and child level status = Closed<\/code>
then you must send the filters in the correct order:&p_fset=0&p_fieldName=STATUS&p_value1_EVDISPLAY=Open&p_fset=1&p_fieldName=STATUS&p_value1_EVDISPLAY=Closed<\/code>
and you can then use:&p_fset=0&p_fieldName=STATUS&p_fset=1&p_fieldName=STATUS&p_value1_EVDISPLAY=Open&p_value1_EVDISPLAY=Closed<\/code>
or alternatively:&p_fset=0&p_fset=1&p_fieldName=STATUS&p_fieldName=STATUSS&p_value1_EVDISPLAY=Open&p_value1_EVDISPLAY=Closed<\/code>
Both the above will work as long as p_fset=0<\/code> and p_fset=1<\/code> are in the same order as: &p_value1_EVDISPLAY=Open and &p_value1_EVDISPLAY=Closed<\/code>
If you want the base level filter to be Open<\/code> and the child level filter to be Closed<\/code> programming arrays are built:p_fset[]= {0,1}
\np_fieldName[] = {STATUS, STATUS}
\np_evdisplayvalues[] = {Open, Closed}<\/code>
This shows why the order of the parameters matter.<\/li>\np_fset<\/code> parameters to specify the hierarchy levels.\u00a0 The base hierarchy level is set with p_fset=0<\/code>:
\nuser_id=user_id<\/code>
\n&password=xx<\/code>
\n&statevar=run_report<\/code>
\n&report_id=711<\/code>
\n&API_REVERSE_LOOKUP=YES<\/code>
\n&p_ql_search_mode=ADVANCED<\/code>
\n&p_fset=1<\/code>
\n&p_fieldName=PRIORITY<\/code>
\n&p_operator==<\/code>
\n&p_value1_EVDISPLAY=P%202<\/code>
\n&p_mvalue1=<\/code>
\n&p_fset=0<\/code>
\n&p_fieldName=PRIORITY<\/code>
\n&p_operator==<\/code>
\n&p_value1_EVDISPLAY=P%203<\/code>
\n&p_mvalue1=<\/code><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"