You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.Create an integration account or use existing integration account which is one time setup. Select the pricing tier as standard.
a) To link integration account to logic app.
a) In integration account's navigation menu, under Settings, select Callback URL.Find the Generated Callback URL property value, copy the value, and save the URL to use later for linking.
On your logic app's navigation menu, under Settings, select Environment variables.On the Environment variables page, check whether the app setting named WORKFLOW_INTEGRATION_ACCOUNT_CALLBACK_URL exists.
If the app setting doesn't exist, at the end of the settings list, add a new app setting by entering the following:
"WORKFLOW_INTEGRATION_ACCOUNT_CALLBACK_URL":""
b) In the Logic App, navigate to Artifacts > Maps, click on "Add", and upload a XSLT map.
c) In the Integration account, navigate to Settings > Maps, click on "Add", and upload a XSLT map.
2.Open the designer and incorporate an HTTP request trigger.
Insert an Transform XMl action.
For the content you wish to validate, add the code ()(add without brackets).
Set the Maps Source to Logic App.
For the Map Name, select the XSLT map that has been uploaded to the Logic App.
Implement a Response action with a status code of 200. For the body, use the "Transformed XMl output" token from the Transform XMl action.
Save the workflow.
Launch Postman.
Choose "Post" and input the workflow runtime URL. Press send.
**Expected:**Run should get success in the run history.
Actual: Run in the run history is in running state and there are some logs present.
[2024-10-09T12:45:00.192Z] Job error: correlationId='235186b2-6cab-4ebc-8d5f-1e4a9d2d109c', operationName='XsltActionJob.ExecuteAction', jobPartition='AEBD9F620F854862A7DE528FDF8F3365:2D08584731289912163486663915045CU00', jobId='08584731289912163486663915045CU00', message='XsltActionJob failed with unexpected exception.', exception='System.InvalidCastException: Unable to cast object of type 'Microsoft.Azure.Workflows.Data.Configuration.EdgeFlowSqlDataProviders' to type 'Microsoft.Azure.Workflows.Integration.Configuration.IntegrationAccountFlowDataProviders'.
[2024-10-09T12:45:00.195Z] at Microsoft.Azure.Workflows.Integration.Extensions.IFlowConfigurationHolderExtensions.GetIntegrationAccountFlowDataProviders(IFlowConfigurationHolder holder)
[2024-10-09T12:45:00.198Z] at Microsoft.Azure.Workflows.Integration.Extensions.IFlowConfigurationHolderExtensions.GetIntegrationAccountDataProvider(IFlowConfigurationHolder holder, IntegrationAccountInformation integrationAccount)
[2024-10-09T12:45:00.205Z] at Microsoft.Azure.Workflows.Worker.Jobs.XsltActionJob.GetMapContentLink(ArtifactInformation map)
The text was updated successfully, but these errors were encountered:
vgouth
changed the title
SQL Based: XML XSLT transformation success from integration account having more logs
SQL Based: XSLT transformation success from integration account having more logs instead of success run
Oct 9, 2024
Describe the Bug with repro steps
**Prerequisites: **
1.Create an integration account or use existing integration account which is one time setup. Select the pricing tier as standard.
a) To link integration account to logic app.
a) In integration account's navigation menu, under Settings, select Callback URL.Find the Generated Callback URL property value, copy the value, and save the URL to use later for linking.
On your logic app's navigation menu, under Settings, select Environment variables.On the Environment variables page, check whether the app setting named WORKFLOW_INTEGRATION_ACCOUNT_CALLBACK_URL exists.
If the app setting doesn't exist, at the end of the settings list, add a new app setting by entering the following:
"WORKFLOW_INTEGRATION_ACCOUNT_CALLBACK_URL":""
b) In the Logic App, navigate to Artifacts > Maps, click on "Add", and upload a XSLT map.
c) In the Integration account, navigate to Settings > Maps, click on "Add", and upload a XSLT map.
2.Open the designer and incorporate an HTTP request trigger.
**Expected:**Run should get success in the run history.
Actual: Run in the run history is in running state and there are some logs present.
What type of Logic App Is this happening in?
Standard (VSCode)
Which operating system are you using?
Windows
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos
Logs:
[2024-10-09T12:45:00.192Z] Job error: correlationId='235186b2-6cab-4ebc-8d5f-1e4a9d2d109c', operationName='XsltActionJob.ExecuteAction', jobPartition='AEBD9F620F854862A7DE528FDF8F3365:2D08584731289912163486663915045CU00', jobId='08584731289912163486663915045CU00', message='XsltActionJob failed with unexpected exception.', exception='System.InvalidCastException: Unable to cast object of type 'Microsoft.Azure.Workflows.Data.Configuration.EdgeFlowSqlDataProviders' to type 'Microsoft.Azure.Workflows.Integration.Configuration.IntegrationAccountFlowDataProviders'.
[2024-10-09T12:45:00.195Z] at Microsoft.Azure.Workflows.Integration.Extensions.IFlowConfigurationHolderExtensions.GetIntegrationAccountFlowDataProviders(IFlowConfigurationHolder holder)
[2024-10-09T12:45:00.198Z] at Microsoft.Azure.Workflows.Integration.Extensions.IFlowConfigurationHolderExtensions.GetIntegrationAccountDataProvider(IFlowConfigurationHolder holder, IntegrationAccountInformation integrationAccount)
[2024-10-09T12:45:00.205Z] at Microsoft.Azure.Workflows.Worker.Jobs.XsltActionJob.GetMapContentLink(ArtifactInformation map)
[2024-10-09T12:45:00.208Z] at Microsoft.Azure.Workflows.Worker.Jobs.XsltActionJob.ExecuteAction(FlowRunActionExecutionContext actionExecutionContext)', organizationId='', activityVector='IN.03', additionalProperties='{"ParentActivityId":"00-51c7bbcd25d8d2bcf2e3e7b2d2422071-2a8b6c60e5e57af6-00"}', extensionVersion='1.94.1.0', siteName='UNDEFINED_SITE_NAME', slotName='', activityId='3e2431a1-61b1-4c0f-ab39-77bdb33e292e'.
Browser
VS Code
Additional context
VSIX Version: 4.96.0
The text was updated successfully, but these errors were encountered: