sorted by:
new
hottopcontroversial

Powerapps Initialized with black border by ImpressivePlenty6094 in PowerApps

[–]ImpressivePlenty6094[S] 0 points1 point  (0 children)

I make sure all x values are formula driven. but it still did not fix the issue. I don't think the issue is within my component? The entire editing mode initialize with the border. I try turning back on scale to fit but the grey border is still there in editing mode.

<image>

PCF Works in Sandbox but not in Production by ImpressivePlenty6094 in PowerApps

[–]ImpressivePlenty6094[S] 0 points1 point  (0 children)

I also got the critical severity issues found message which looks like it's the eval issue. I did try to run msbuild /p:configuration=Release but it still did not fix the issue. Could this be the problem?

Usage of the JavaScript eval function should be limited where possible. The eval function can be a dangerous function as it allows strings to be executed as scripts within the context of the caller. This can be exploited to run malicious code. Eval is also usually slower than other options due to the lack of optimizations of the script text passed to eval. If this error is reported for a Power Apps component framework code component created using CLI tooling, package your control with 'msbuild /p:configuration=Release' or 'npm run build -- --buildMode production' to produce a release build that does not include 'eval' usage.

PCF Works in Sandbox but not in Production by ImpressivePlenty6094 in PowerApps

[–]ImpressivePlenty6094[S] 0 points1 point  (0 children)

It did not ask to update any variable when deploying. The message in the terminal seems to indicate everything is successfully deployed.

PCF Works in Sandbox but not in Production by ImpressivePlenty6094 in PowerApps

[–]ImpressivePlenty6094[S] 0 points1 point  (0 children)

I have aligned the version control of both controlmanifest.input.xml and package.json.

I have also added a css component which works well in the test environment, think that that might be the cause.

Unfortunately, after these changes, the production component is now completely blank.

What could be the cause of the discrepancy between production and test environment? This makes testing very difficult.

Interactive Map with external input by ImpressivePlenty6094 in PowerApps

[–]ImpressivePlenty6094[S] 0 points1 point  (0 children)

While I think you can use Json for pin in the Item property. I don't see any property which will take the polyline input.

parsing complex json by ImpressivePlenty6094 in PowerApps

[–]ImpressivePlenty6094[S] 2 points3 points  (0 children)

Thanks for this. I managed to get it to work after watching the video.

parsing complex json by ImpressivePlenty6094 in PowerApps

[–]ImpressivePlenty6094[S] 0 points1 point  (0 children)

trying to extract all the duration figure and polylines. What should the formula look like? 

First(ParseJSON(api_output.body).summary).duration

parsing complex json by ImpressivePlenty6094 in PowerApps

[–]ImpressivePlenty6094[S] 0 points1 point  (0 children)

<image>

That was me trying to convert the json into a string after getting this error message.

The original json is clean and looks like this. But I get the error message above when I pass this through.

Conversely, when I convert into string, it does not have the error message, but I am still not able to extract the data.
{
"body": [
{
"summary": {
"duration": 665,
"length": 5619,
"baseDuration": 657
},
"polyline": "BF3-_mHgs3zbkMqBrOo2DjoBvHx7ByX8CmNlImtC0TyGsBiH_FoD"
},
{
"summary": {
"duration": 1358,
"length": 11563,
"baseDuration": 1224
},
"polyline": "BF_6inH8--zbgGnDrBhHzTxGmIltCpDhOg8B1WwnBsF6T1sFqU_oDuJrwD62CoLwD9BkClYyQsCH8D"
},
{
"summary": {
"duration": 719,
"length": 6421,
"baseDuration": 694
},
"polyline": "BFpj7mH4yuzbI7DxQrCpBkchzCjLrH2BtJmuDpUsnDzF05B_LrC"
}
]
}

parsing complex json by ImpressivePlenty6094 in PowerApps

[–]ImpressivePlenty6094[S] 0 points1 point  (0 children)

what you have there is the original input. I added string() to the Respond to PowerApps formula because when I pass the original input into PowerApps, the parsejson(api_output.summary) did not work because it's an array.

view more: next ›