Hey there,I’m assuming that you’re looking into XM Functions to do this, hence the 45s time limit. Unfortunately, this is a hard limit that we cannot increase so we’ll have to find some other way of doing what you want to do. Generally speaking there are two main paradigms when it comes to developing for workflows. We have the long-running workflows like the SFSF extractor that operate on larger datasets, and we have more event-driven workflows using a webservice task that operates on a single record. While XM Functions allows you to work somewhere in between, it isn’t designed for the long running large dataset use cases. On the Export function, it’s simply to export a calculated value to the next task. In the next task, if it has an option to pipe data, you’ll be able to choose the export from a previous task as well. That’s how you ingest to another task. What I’d recommend is to come to an office hours with my team. From your profile, I see that you’re part of QPN. Can you please u
Hi @JesperAndersen The qualtricsApiFetch method should now work for delete-participant in ex-projects now. Give it a shot and let me know if you run into anything else.
Hi @JesperAndersen I’m going to have our teams look at this, but in the meantime, using context.client.fetch does actually work for this API. The downside is that you have to take in a client credential to do it, so using the generic fetch may not work. Let me know.deleteParticipantBody = ['email@domain.com'];const fetchPostResponse = await context.client.fetch(`https://yul1.qualtrics.com/API/v3/ex-projects/${projectId}/delete-participants`, { method: 'POST', body: deleteParticipantBody, connection: { connectionName: 'connName', paramFormat: 'header', paramName: 'X-API-TOKEN', paramTemplate: '%s' } });
Hi @JesperAndersen thanks for reporting this. We took a look and have made a few changes to the submission process. Can you give things another try?
Hi!Any time you see plugin client methods and are wondering what they do, take a look at the Plugin Client reference documentation.Here’s the section for getText. Basically, it’s referencing the translations files. Depending on what level you’re calling getText for (at the Extension level or Plugin level) the translations files will be in different locations, but you’re generally looking for something like EN.json.
Can you please put in a feature request in Evolve?
Yep, that’s exactly it. We have a few different ways of sharing with your customers: Private extensions are usually going to be 1:1 bespoke for your client. The contract is between you and the client, so this doesn’t have to go through certification. If you would like to, you are absolutely welcome to request certification from our team as well, but definitely not required. Public extensions will typically result in a listing on our XM Marketplace and do need to be certified. There are some stark differences when it comes to sharing with the two types of extensions. With private, a brand admin of your customer has to be on your extension team. Then you can share with their brand.With public extensions, you can preview your extension with a number of customers without adding them to your developer team. The assumption is that you’ll preview with your customers and then eventually release a new, updated GA version that will go to everyone.Hope that helps!#LetsGoBuildXM!
Currently, XM Solutions only support these resources. We’re working on adding more resources as time goes by, but please enter your idea in Evolve (the Ideas section here in XM Community) so we can keep track of interest. For now, you’ll have to remove anything xFlow related. Thanks!
Both the npm and bin folders should have been created for you by default. When you install node, it should be bundled with npm already, so it should create the %APPDATA%\npm folder by default. When you install @qualtrics/solution-cli, it should create (if not already there) an %APPDATA\npm\bin folder which is NOT added to %PATH% by default (I know you added this to %PATH% already). Dumb question, but you’ve closed and re-opened your PS terminal since changing the PATH right? $Env:Path includes your \bin folder right?You basically need to find where solution-cli was installed. If you find it and navigate to the folder within PS, can you run the solution.exe command? If that works, and $Env:Path shows the folder where the solution.exe executable is, there’s no reason this wouldn’t work.
Oh, right. Of course. Let me look into this. Are you trying to conditionally create something? If so, what and what else are you doing in solutionExecution.json?
Hi @DamienP ! Have you tried using the square brackets without quotes? "condition": [setup.answers.Survey3, false],Give that a shot and let me know how it goes. Hubert
Hey Christopher,We ran the Windows version of xmt through our scans once more just in case. Our scans came back negative, so we believe it’s a false positive. I’m going to DM you.
Hey!There are a few things that need to be running. For a workflow task, you’ll need to have ‘npm start’ running in the plugin directory and `xmt develop extension` running in the extension folder. Hope that helps,H
Hi CLM,In general, it's not recommended for an external application to write directly into your database and we don't have any tasks to support that. You'd need an intermediary like a load data into SFTP task and then another system on your side to load the data from your SFTP into MySQL. If this is still a use case you need to solve for, what are you trying to query inside MySQL? Perhaps you can achieve the same outcome inside Qualtrics.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
