Since the default map-control in Power Apps delivers information about selected areas in the form of geoJSON, we had to make sure our Fabric Data agent was expecting this as a part of the initial request. Unfortunately, the controller also delivers the locations as an array if there are multiple elements, and this is not a valid geoJSON format. So we had to describe in detail how it should handle this situation.

GeoJSON data from the default map controller in Power Apps

An issue with the geoJSON format is that it does not support circle figures, which is a problem as this is a standard way of selecting coordinates within the standard Power App map controller. What causes this to be a problem is the fact that it is only considered a single point on the map, with a “radius” property indicating the size of the circle.

Our Fabric Data agent interpret this as a distance in meters and fail while trying to find the locations as this is a different method of measuring distance than geological coordinates. After manually measuring geolocations on the map, we managed to find out the “radius” property is fairly translatable to the geolocations.

For example, if the “radius” is set to 1000 then, also assuming the center point is located at [20.00000000, 20.00000000], we could fairly assume the points furthest north, east, south and west would be:

[
[20.00001000, 20.00000000],
[20.00000000, 20.00001000],
[19.00999000, 20.00001000],
[20.00000000, 19.00999000]
]

Using this knowledge, we also instructed to the agent to find resources within those coordinates. This is dirty way of solving this as it effectively measure a square rather than a circle, but the vast majority of the circle will be covered and even in real-life scenario it would most likely work as an acceptable workaround

The Data agent in Fabric with instructions and response to the JSON string sent from the Power App displayed in the picture above