Answered

Importing address from a Multiple Text Fields component in JotForm to Dataverse

(1) Share

Report

Posted on by EricArcher33

Hello everyone!

I am using Jotform for data intake and using a flow to import a new row to a Dataverse table. I am struggling to get the grouped fields in Jotform to import to separate fields in my table.

Address for instance. In JotForm it is a single component that contains all of the necessary fields:

However it populates it all into a single comma separated field:

I have tried using copilot to create an expression in Power Automate that will only pull a specific value from the comma separated field.

This was to pull the City component: split(triggerOutputs()?['body/19 - Traveler Address'], ',')[2]

but now I am getting an error:

And now I also realize that if the address 2 line is left blank, then it is simply omitted and then my indexed numbers would pull the wrong data. I tested the flow with data in all fields and still got this error. I am new to all of this, but I know it should be possible!

What is interesting is that when I export the data to Excel from JorForm, all of the fields are separated into their own columns. I am hoping to be able to do this in real time with the new submission flow trigger and not have to do daily batch imports manually with excel.

So my real question is: What is the proper way to import this type of data from JotForm through a triggered flow into the correct fields in Dataverse?

Categories:

AI Builder

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

Mark Nanneman 991 Super User 2025 Season 2 on at

Like (1)

Report

The reason your flow is failing (the error in the screenshot you posted) is because it's assuming there's at least 3 items in the array after you split by ','. Generally, you don't want to reference an item in an array by putting an integer in [ ] unless you're positive it's always going to have a certain number of items in every run. When you're dealing with addresses, they just will not always have the same number of items when you split by a comma (due to multiple street lines, etc.)

It's better to use methods like last(), first(), take(), skip()
e.g. Last(split(<string>,<delimiter>)) if possible--but that probably wouldn't be helpful here with addresses.

I'd consider using something like an AI Builder GPT action to extract the city name and zip code from the address and output it in a JSON, or a Bing Maps connector (or other map API) to just lookup the address from whatever JotForm sends. That or you could just redo the JotForm and not use the built-in Address node. Build your own questions for Address Street, City and State and Zip.

I've done a few JotForm flows in the past, and other flows using different survey form management platforms. You're giving me deja vu of some of the issues. I recall JotForm having some quirky behaviors--like you might have had the option to change the format of the data you get from the power automate trigger? There might have also been a way inside JotForm to edit how certain data is returned to power automate.

Any chance you could send some screenshots of the trigger setup, and also can you look at a flow run and check the raw output from the JotForm Trigger?

Double check that the address details aren't present twice in different formats.

Was this reply helpful? Yes No
EricArcher33 20 on at

Like (0)

Report

Thanks @Mark Nanneman the simplest solution that solves the problem at hand is to simply create my own separate address fields and map them directly to the Dataverse table columns, so for now this will get me functional!

I considered AI builder, but that seems overkill to solve a connection issue between 2 processes that I am purpose building, though I will be exploring that route for some other needs on this project.

I will dig into JotForm customizations a little more too, there might be some good options there to increase compatibility.

Was this reply helpful? Yes No