Hey Ola, 

If you are for example using the native NetSuite integration you are able to publish a button to a board, which you can use to trigger an import manually. You just need to create an import and save the configuration. 

Pigment has such a wide variety of native connectors that I have not needed to use the API Request integration myself, but I have worked with another EPM tool in the past that was not as flexible and a common trick I used was to create an Azure Logic App or an Azure Function App, which can be used to execute scripts for data imports etc. Logic App and Function App both allow HTTP-triggers, which means that you could publish the URL-trigger to a board and use that to trigger whatever scripts you want. 

Hope this helps :) 

Thanks, but in this case the question is just related to how the data team can trigger an import after a import file has been prepared in Amazon S3. They fear that the data volumes will be to big to include everything in a single request, and hence they like to prepare a file and then just make a request to the API to trigger a file import.  

Hi, bumping this request. 

It would be nice to be able to make a call to Pigment to execute an import configuration that uses an external source (Azure SQL in our case) without having to pass the data in the API call. When my data processing job has completed in SQL I just want to make a simple call to Pigment to say run this import configuration.

Hey Ola, 

If you are for example using the native NetSuite integration you are able to publish a button to a board, which you can use to trigger an import manually. You just need to create an import and save the configuration. 

 

Pigment has such a wide variety of native connectors that I have not needed to use the API Request integration myself, but I have worked with another EPM tool in the past that was not as flexible and a common trick I used was to create an Azure Logic App or an Azure Function App, which can be used to execute scripts for data imports etc. Logic App and Function App both allow HTTP-triggers, which means that you could publish the URL-trigger to a board and use that to trigger whatever scripts you want. 

Hope this helps :) 

This is a workaround, and not a solution. The goal here of the request is to be able to tell pigment to do the data pull through an API call FROM THE ETL TOOL, not initiated within Pigment. 

Currently, the only way you can do that through an API is by also passing the data in a CSV (even if you have an import configuration set up that is a direct connection).

The ideal solution is a new API call that will execute an import configuration which already has a source defined (netsuite, etc.) WITHOUT having to pass the CSV file. 

That way, when your nightly processing is finished running you can simply call your array of API’s in Pigment to tell it to refresh according to the import configurations already defined in Pigment without having to stage the data in CSV and send it inside the API.