Publish To Tableau Server Alteryx Download |VERIFIED|

0 views

Skip to first unread message

Veola Delzell

unread,

Jan 20, 2024, 1:40:49 PM1/20/24

to stararulti

My client was asking me to find a way to publish the Alteryx result sets into Tableau server from where i could use the published data source which in turn Users could build the visualization on their own in the tableau server directly . I was able to achieve this solution using Event Run command Options

publish to tableau server alteryx download

Download Zip >>>>> https://t.co/oouoGZfb2o

By inputs do you mean what you've typed into the tool's configuration? Remember that this is the information used to log in to your Tableau Server - do you typically type in a domain before your user name? Also for the Server URL there should be no Site name included. So it should look something like _tableau_server_URL or _tableau_server_URL. Then you can either leave Site field blank for Tableau Server's default site or put a site name.

Alternatively, you can publish a data source in multiple parts. To do that, you initiate a file upload by calling Initiate File Upload, send portions of the file to the server using Append to File Upload, and then commit the upload by calling Publish Data Source. In this case, Publish Data Source doesn't contain the file to publish.

HTTP status error Code Condition Details 400 400000 Bad request The request message is missing or incomplete, or contains malformed XML. Make sure that the Content-Length value is set. 400 400000 Missing data source There is no attachment in the request for the data source. 400 400008 Invalid overwrite value The overwrite parameter must be set to true or false. 400 400008 Invalid append value The append parameter must be set to true or false. 400 400008 Invalid embed value The request body contains a element and it has an embed attribute whose value is not true or false. 400 400010 Invalid data source filename The name of the data source file did not end with the suffix .hyper, .tds, .tdsx, or .tde. 400 400010 Missing or invalid file type The request included an uploadSessionId parameter but no file type, or the file type was something other than hyper, tds, tdsx, or tde. 400 400010 Unexpected attachments The message had both a uploadSessionId parameter and an attachment, or the message contained more than one attachment. 400 400011 Publishing error The data source could not be published for some other reason than those specified earlier. 400 400019 Malformed request body The request message is missing or incomplete, or contains malformed XML. Make sure that the Content-Length value is set. 400 400055 Incompatible overwrite and append values The overwrite and append parameter cannot both be set to true. 400 400129 Invalid Ask Data enablement The enablement setting in the request body is not valid for the current server configuration. 403 403007 Insufficient publishing permission A non-administrator user attempted to publish a data source, but the caller doesn't have sufficient project permissions. 403 403007 Unlicensed publishing forbidden A non-administrator user who is unlicensed attempted to publish a data source. This is disallowed for all projects (including the default project). 403 403007 Overwrite forbidden A data source with the specified name already exists and the overwrite parameter was not set to true. 403 403007 Problem connecting to data source There was a problem connecting to a data source. This can be due to missing or invalid connection credentials or because the referenced data source is not available on the server. 403 403008 Insufficient storage quota The data source could not be published because there is not enough storage remaining on the server to accommodate its size. 404 404000 Site not found The site ID in the URI doesn't correspond to an existing site. 404 404004 Data source not found The append parameter is true but the data source name specified in the request body does not correspond to an existing data source. 404 404005 Project not found The project ID in the request body doesn't correspond to an existing project on the site. 404 404015 File upload not found The file upload session ID in the request body doesn't correspond to an existing file upload on the site. 405 405000 Invalid request method Request type was not POST. For more information, see Handling Errors.

To publish a flow in multiple parts, you initiate a file upload by calling Initiate File Upload(Link opens in a new window), send portions of the file to the server using Append to File Upload(Link opens in a new window), and then commit the upload by calling Publish Flow. In this case, Publish Flow doesn't contain the file to publish but the uploadSessionId and the flowType parameters are required.

Users who are not server administrators or site administrators can publish a flow only if the flow belongs to a project that they have permissions to publish to, have a site role that allows publishing and have write permissions on the flow this is an overwrite.

HTTP status error Code Condition Details 400 400000 Malformed request body The XML content in the MIME multipart request is not empty. 400 400089 Missing flow name Flow name is required and was not specified. 403 403007 Invalid permissions The caller does not have the necessary permissions to publish the flow. 400 400090 Missing flow payload The flow information (the structure containing the flow description, flow project) was not included in the request body. 400 400086 Invalid flow attachment The name of the flow doesn't end in .tfl or .tflx. 400 400087 Generic flow publishing error The flow could not be published for some other reason than those specified earlier. 409 409041 Flow already found in destination The flow name should be unique, or the overwrite flag parameter should be set to true. 403 403008 Insufficient storage quota The flow could not be published because there is not enough storage remaining on the server to accommodate its size. 404 404000 Site not found The site ID in the URI doesn't correspond to an existing site. 404 404005 Project not found The project ID in the request body doesn't correspond to an existing project on the site. 404 404027 Flow not found The flow ID in the URI doesn't correspond to an existing flow. 405 405000 Invalid request method Request type was not POST. For more information, see Handling Errors.

Alternatively, you can publish a workbook in multiple parts. To do that, you initiate a file upload by calling Initiate File Upload, send portions of the file to the server using Append to File Upload, and then commit the upload by calling Publish Workbook. In this case, Publish Workbook doesn't contain the file to publish.

api-version The version of the API to use, such as 3.21. For more information, see REST API and Resource Versions. site-id The ID of the site to publish to. overwrite-flag (Optional) true to overwrite a workbook that has the same name, or false to fail if the specified workbook already exists. The default is false. If overwrite-flag is set to true but the workbook doesn't already exist, the operation succeeds. asJob-value (Optional, boolean) If false, the workbook publishing process runs as a synchronous process. If a workbook is very large, the process might time out before it finishes. If you set this value to true, the process runs asynchronously, and a job will start to perform the publishing process and return the job ID. You can check the status of the import job by calling Query Job. Default value is false. skip-connection-check-flag (Optional, boolean) If true, then the Tableau server will not check if a non-published connection of a workbook is reachable.Publishing will succeed but unchecked connection issues may result in a non-functioning workbook. If you encounter this issue, followKeep Data Fresh guidelines(Link opens in a new window). Default value is false. upload-session-id If you are calling this method to commit a file that was uploaded in parts, this value contains the upload session ID that was generated by a call to Initiate File Upload. If this value is not included, the server assumes that the body of the request contains the file to be published. workbook-file-type twb or twbx to indicate whether you have uploaded a workbook file (twb) or a packaged workbook file (twbx). This value is required if you are calling Publish Workbook in order to commit a file that was previously uploaded using Append to File Upload. The value is not used if you upload a file in the body of the request.

HTTP status error Code Condition Details 400 400000 Malformed request body The XML content in the MIME multipart request is not empty. 400 400000 Missing workbook There is no attachment in the request and no uploadSessionID parameter. 400 400000 Unexpected attachments The message had both an uploadSessionId parameter and an attachment, or the request body contained more than one attachment. 400 400008 Invalid embed value The request body contains a element and it has an embed attribute whose value is not true or false. 400 400008 Invalid overwrite value The overwrite parameter must be true or false. 400 400011 Publishing error The workbook could not be published for some other reason than those specified earlier. 400 400020 Invalid workbook file name The name of the workbook doesn't end in .twb or .twbx. 400 400035 Missing or invalid file type The request included an uploadSessionId parameter but no file type, or the file type was something other than .twb or .twbx. 403 403007 Insufficient publishing permission A non-administrator user attempted to publish a workbook, but the caller doesn't have sufficient project permissions. 403 403007 Unlicensed publishing forbidden A non-administrator user attempted to publish a workbook. This is disallowed for all projects (including the default project). 403 403007 Overwrite forbidden A workbook with the specified name already exists and the overwrite parameter was not set to true. 403 403007 Problem connecting to data source There was a problem connecting to a data source used by the workbook. This can be due to missing or invalid connection credentials or because the referenced data source is not available on the server. 403 403008 Insufficient storage quota The workbook could not be published because there is not enough storage remaining on the server to accommodate its size. 403 403130 Publishing overwrite A workbook with the same name already exists. 403 403131 Concurrent update The workbook is already being published in another process. 403 403132 Failed connection check One or more data sources used by the workbook could not be reached. 404 404005 Project not found The project ID in the request body doesn't correspond to an existing project on the site. 404 404006 Workbook not found The user specified overwrite as true but no workbook with the specified name exists on the site. 404 404015 File upload not found The file upload session ID in the uploadSessionId parameter doesn't correspond to an existing file upload on the site. 405 405000 Invalid request method Request type was not POST. For more information, see Handling Errors.