This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.

Just upgraded to Alteryx Server 2018.4. also downloaded latest alteryxserverusagereport.zip from download portal. I configured the tool correctly and I get a Tableau workbook with data, except for the last dashboard called 'Alteryx Server | Usage'. Looking at datasource behind the sheets in the viz, there are missing fields such a NewUsers, SerialNumber, ServerDataTime, StoppedUsers,tool_group, Count.

Looking at Alteryx_Server_Usage_Report.yxmc, the nested macro "RunBatch.yxmc" throws an error. Inside this macro the error seems to a batch file in the run command tool:

We don't have that checkbox checked. See screenshots. Error is in Collection Check tool container which contains only one tool - the runbatch macro. This macro is fed by multiple interface tools but not the check box for 'Enable Desktop Usage Report'. IMHO, it has to be one the actions in this macro since I did get it to work by

hardcoding the command args in the top Run command tool (AlteryxGallery Query).

You are correct that the "AlteryxServer | Usage" tab of the Tableau workbook is not populated. That tab refers only to usage from the Designer and won't be populated unless you have done all of the below.

I wasn't able to view your screenshot of the macro configuration in the workflow itself. That's what @AngelaO was referring to:

Make certain that you've either unchecked the box on the main macro configuration OR that you've configured the RuntimeSettings.xml as described on the help page that is linked above.

If you have not amended the RuntimeSettings.xml, reopened Designer, and run a workflow from there, you won't have any data in the "AlteryxServer | Usage" tab of the Tableau workbook.

Please note that the errors you're observing in the RunBatch.yxmc are because you did not set the debug values within your submacro, so it's still using the default values rather than pulling the correct path from the RuntimeSettings.xml as it would if you'd run it from the full workflow.