Hi Clemens,
You can do a bit of a workaround using the Library Supplemental Data Sources.
If you can create a file you can use these steps:
- Create a standalone Workflow:
- Extract Data from Qualtrics File Service
- Load to SDS Task
If you can’t create a file you can use these steps:
- Create a Imported Data Project
- Import data to the project using the Add Records to Imported Data Project API
- Create a workflow
- Extract Data from Data Project Task
- Load to SDS Task
@conotho : Thanks a lot for your answer!
Consider the webservice as mandatory. Is there a workflow from getting the webservice result into a file, which I can store in the File Service?
Regarding Solution 2: IDP API would be not supported by our IT, I have to use the Webservice Task result.
@conotho : Thanks a lot for your answer!
Consider the webservice as mandatory. Is there a workflow from getting the webservice result into a file, which I can store in the File Service?
Regarding Solution 2: IDP API would be not supported by our IT, I have to use the Webservice Task result.
@Clemens Your Webservice Task return your list as a JSON object, the SDS need table format (csv, tsv,…….) so that’s why you need IDP as middle man.
Hi @Clemens,
I am curious what webservice you are referencing here? Which call are you requiring?
Consider the webservice as mandatory. Is there a workflow from getting the webservice result into a file, which I can store in the File Service?
In the Qualtrics File Service solution, you would be using a secure and isolated file store API. If you IT team is requiring the use of webservice, it is likely that they will support the Qualtrics File Service as well as long as they can produce a table.
In the solution that includes the IDP, step two would be using a webservice task in the workflow, so I do believe that it would meet your teams requirements!