Hi Sean, sorry if I'm oversimplifying this, but can you put the CSV data into an Excel Online or Google Sheets worksheet; call that worksheet in a scenario, then use an iterator to cycle through each row in the worksheet, each time using the "Add/Replace a Record" action on the data store module?

It should just be available as an output from your trigger module - no need to set a custom variable. You can see in my example, I didn't do anything to make it available. You may have to run the scenario in order for the trigger module to know what outputs it can make available to downstream modul...

I believe that's what Fusion uses to compare the old value and new value of properties that may have changed on the record update, so you can perform logic based on the change itself if needed. My first module after the trigger event is a read record, where I read the user record based on newstate....

We tried doing it off something like the value of login count or last login date having changed, but those didn't trigger the scenario as expected. I ended up putting a calculated field on the user form "useAlias" that is either true or false depending if the preferred first or preferred last name ...

Hi Jason, that may have been one of my posts. And, that's very similar to how we do it (trigger on user update). We used to run it on a schedule, but users were confused as to why they sometimes (briefly) saw the "wrong" name. What is it that concerns you about that approach, or leads you to wonde...

Adina, you got your wish!I'm surprised they haven't come in and changed this from Seeking Votes to Delivered...

Now that Workfront has delivered on exporting custom forms, we'd like this action possible to call from the API. Therefore asking for your support of this idea: https://one.workfront.com/s/idea/0874X000000oOB0QAM/detail We want to perform this action in bulk as part of a Fusion automation, but canno...

It's wonderful that this can now be done. But! We would like to do this via the API as part of an automated process. Please take a moment to vote for this related request that will enable this function via the API:https://one.workfront.com/s/idea/0874X000000oOB0QAM/detail

Now that Workfront has delivered on exporting custom forms, make this action possible to call from the API. We want to perform this action as part of an automation, but cannot because it can only be performed directly in the web interface, one record at a time.

I think Doug and I interpreted this question differently. What I read is:"For a custom form in my instance, show me the list of custom fields that exist on that form, and if a custom field is a dropdown, multi-select checkbox, or radio button, tell me what are the possible options a user may select ...