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.
Do you use Alteryx in a language other than English? If so, we want to hear from you! Please help us improve the international experience of our products by participating in this 5 minute survey.
We are updating the requirements for Community registration. As of 7/21/21 all users will be required to register a phone number with their My Alteryx accounts. If you have already registered, you will be prompted on your next login to add your phone number.
The Alteryx Gallery can support custom reports in .rptx format. If a workflow or app is uploaded to the gallery without taking the following steps, there will be an error stating that it can not find the .rptx file. The key is to make sure to save a copy of the .rptx file in the same location as the App so that the allocate report configuration is not lost. Then make sure to add the RPTX file as an asset attached to the Allocate Report tool before publishing to the gallery. To do this, first make sure that the Display Asset Management in Properties Window option is checked in Designer User Settings:
Now click on the Assets icon on the left side of the Allocate Report configuration window, and add RPTX file:
It is important to know that Custom VVFs are not supported in the Gallery. If there is a custom variable that you would like to include, it must be calculated inside the .RPTX file itself. Calculating a Variable inside an RPTX: Opening an RPTX in the Composer will display the code that drives the custom report by adding code similar to the following, a new variable can be calculated within the RPTX itself. <td align="Left" width="17%">My Variable </td> <td align="Right" width="8%"> <all:app class="__format2" formula="(XCYFEM + XCYMALE)" /> </td>
The Composer File (pcxml) is a file type that contains a proprietary language used by Alteryx for reporting purposes. What this means for use in the Gallery is that an end user will have the ability to choose among XLSX, PDF, DOCX, ZIP and HTML file types for output.
In order to use the pcxml format, you will need to use the Render tool, which can be found in the Reporting section of the tool palette. A basic Table tool connected to the Render tool will suffice for a grid report, shown respectively.
The configuration for the Render tool will require two things, first, that the Output Mode is set to choose a Specific Output File. The Gallery validation of the workflow will fail in the Public Gallery unless a specific output is set. Next, select the pcxml file type for output and name the file. Upon loading the workflow to the Gallery you’ll see that the dependency changes to an externals path “_externals\1\name.pcxml”, this is expected. The second configuration property to set is the Data Field in the Report Data section. We will need to reference the table created using the basic Table tool.
Now load the workflow to the Gallery and that’s it! Enjoy the flexibility of reporting file formats the pcxml Composer file has to offer!
Note: Workflow and all images created in this article are from Alteryx version 10.1
Client Services Representative