Seeking Feedback for new Data Mapper

jeroenjansenoliver-itnl we did have a bug which caused this behavior. Please see my response to hoover1980 for more details. Apologies for the inconvenience.

hoover1980 apologies, we did have an issue in v2.86.2 which introduced the behavior your experienced. The team has had a restrospective and come up with a strategy to avoide future issues.  It was fixed in v2.86.3 after the newer extensions are installed, best to restart VS Code and make sure there are no func.exe processes running (a computer reboot will ensure of this)

Just after my post i reloaded to 2.81.5 which is the first build that checks some depencencies and it worked again. Updated to the latest build and it also worked. I think it has something to do with user or workspace settings that were not correct.

Yes hoover1980 , i have the exact same issue here. I experimented a little bit with also placing the Artifacts folder under the workflow-designtime folder and then i was able to select again and also use the datamapper again. However that does cause side effects that you don't want such as not being able to test, because the generated XSLT will appear on the "project" level and since the Datamapper is then looking at workflow-designtime level, it will not take into account the changes you made. There is some kind of dependency issue there, which i did not have the time to figure out yet. Maybe you can try this workaround to see if this also works for you in the mean while? 

Since the new release i am unable to add a schema to the designer.

Both the "add new"  and "Select existing" option do not work.

Im able to select a schema, but when press save, nothing happens. no error at all

It happens to all logic apps, even new ones.

Removed the extension, readded, tried to change settings in the extension, even reloaded some older extension versions. 

Does anyone else experience this?

edit: i am on version: 2.86.4, vscode version: 1.85.1

jeroenjansenoliver-itnl great to hear, thanks for update

Thanks KentWeareMSFT . Looked like somehow the stack settings of the Logic App were changed to .Net upon deployment. I recreated the Logic App standard, changed the local.settings.json according to your sample and redeployed. Now it works! 

Kind regards,

Jeroen

jeroenjansenoliver-itnl we added the following to the GA blog post. I think it would be good to make changes locally and then deploy based upon the following

Troubleshooting

As we transition from Data Mapper public preview to General Availability, we have merged extensions with the Logic Apps Standard extension. If you have older projects from the Data Mapper public preview, it is recommended to review your local.settings.json file to avoid debugging errors and runtime errors, ensure your local.settings.json reflects the following:

{

  "IsEncrypted": false,

  "Values": {

    "AzureWebJobsStorage": "UseDevelopmentStorage=true",

    "FUNCTIONS_WORKER_RUNTIME": "node",

    "WORKFLOWS_SUBSCRIPTION_ID": "",

    "APP_KIND": "workflowapp"

  }

}

Hi Ken,

Although local set-up and testing works fine locally in VS Code, as soon as i deploy my Logic App project, the deployed workflow does not generate a Workflow URL

A brief overview of the Logic App:

Simple workflow,: request-transformation-reply.

local settings.json

Logic app configuration

Any idea, why this does not work?

Kind regards,

Jeroen

chmthompson there is a function called "Name" that allows you to get the "key" from the source payload. Here is a sample: Logic Apps (Standard) Data Mapper: String functions – SANDRO PEREIRA BIZTALK BLOG (sandro-pereira.com)