Unanswered

PowerApp doesn't accept Location columns

(0) Share

Report

Posted on by Community Power Pla...

I just tried to make a PowerApp connected to a Sharepoint list I made.

Two of the lists columns are Location type ones meant to designate a location I am travelling from and my planned destination so it would calculate the mileage between them.

Unfortunately, I was unable to make the app and got this error message.

{ 

 "status": 400, 

 "message": "The required field \"Destination\" data type is not supported\r\nclientRequestId: db4ffc65-49cb-42bd-9eeb-6704c6bf90a3\r\nserviceRequestId: db4ffc65-49cb-42bd-9eeb-6704c6bf90a3" 

}

Any help please?

Thanks.

Categories:

Building Power Apps

I have the same question (0)

All responses (8)

Answers (0)

Joel CustomerEffective 3,224 on at

Like (1)

Report

@RezaDorrani wrote a blog post about this about 18 months ago. is there any new capability to work with these columns Reza?

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Really?
Can I have the link to that blog post?

Thanks.

Was this reply helpful? Yes No
Joel CustomerEffective 3,224 on at

Like (1)

Report

sorry, thought I posted it https://rezadorrani.com/index.php/2018/12/04/location-columns-for-sharepoint-online-lists-libraries/

Was this reply helpful? Yes No
RezaDorrani 12,143 on at

Like (2)

Report

Hello, No progress made on location type columns. Same behavior to date. Regards, Reza

Was this reply helpful? Yes No
v-yutliu-msft on at

Like (0)

Report
Hi @Anonymous ,

Do you want to calculate the distance between two location columns?

I've made a similar test and found that: it's only supported to calculate the distance between two location columns' cities.

The point is:

Location column display as these columns in powerapps:

'location1: City'

'location1: Country/Region'

'location1: Name'

'location1: Postal Code'

location1: State'

'location1: Street'

The most detailed columns are 'location1: City' and 'location1: Street'.

I try to use 'location1: Street' to calculate distance, but received error.

Using 'location1: City' will work.

Firstly, you need to connect with bing maps.

Then use this formula to calculate:

BingMaps.GetRoute(ThisItem.'location1: City',ThisItem.'location2: City').travelDistance

Then you will get the distance between cities in location1 column and location2 column.

Maybe you want to know more about this function:

https://docs.microsoft.com/en-us/connectors/bingmaps/#get-route

Best regards,

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report
Hello.

After just reading your replies,
I took a stab at it again.

I remade the location columns and added the following secondary columns for each:
Street, City, State, Postcode and Name.

I tried to make the PowerApp again, directly from the Sharepoint list but came across the exact same error as before.
It does not support the overall location columns, even if I only show the subcolumns.

{ "status": 400, "message": "The required field \"Travelling From\" data type is not supported\r\nclientRequestId: f0fc84df-d0d9-4f95-b3c3-7b5f17c0c8dc\r\nserviceRequestId: f0fc84df-d0d9-4f95-b3c3-7b5f17c0c8dc" }

Did I miss anything?

Was this reply helpful? Yes No
TBailey 6 on at

Like (3)

Report

I'm not sure if this is relevant to anyone, but instead of having the address data in the SharePoint List be the "validated" address data, would it suite anyone's needs to instead use the SP List as a data source without validation, and let PowerApps and your App do all of the validation?

For my needs in PowerApps, I do not actually have a reason to utilize the 'address'/location functionality of SharePoint and instead are going to simply use a SP list to hold the location data, as text, without validation, and do all of my data input through the App itself. This way, I can validate addresses, calculate distances, make maps, all with the App, but still use SP lists to hold the data. Luckily the PA platform has address validation built in with the address input control, so it may fit someone's needs to do it this way until M$ creates a working type conversion between SP list 'location' type and PA platform.

Was this reply helpful? Yes No
AA-21032152-0 2 on at

Like (0)

Report

Hello,

Just had this issue and making the location columns not "required" worked on my end. Not ideal but it allowed my flow to work.

Was this reply helpful? Yes No