Is Power Platform administration your thing? Would you like to work on the documentation for it? https://t.co/0QhyY3IsTH
We are hiring https://t.co/hVqY8z6saV.
#PowerPlatform
I'm excited to announce that with the new Application Insights integration you can write Microsoft #Dataverse plug-in telemetry to your Application Insights resource. #powerplatform
https://t.co/ijfg6zOAW1
@MarkMpn@decastroallan@david_rivard People do use the workflow designer for their logic. This was the original 'no-code' design for workflows. You can still create a custom process action without writing code.
But the very common pattern for developers to do everything in plug-ins is better served by custom api.
@graceytech Sorry to be so late to respond. I'm not on Twitter much.
We have a C# sample here:
https://t.co/mWFPg51v9P
Which uses extension on our CDSWebAPIService helper class here: https://t.co/S42GHziVNM
I'm happy to officially announce the release of the new Custom API preview
https://t.co/HqPIiKTKRK
I can't have @MarkMpn stealing my thunder :-)
#CDS#powerapps
@rappen@AltKev@XrmToolBox@imranakram365@rappen Sorry for the delay in responding.
You touched on the key point. Include whatever fields you need in the image, but take the time to think about it before accepting the default. We should see a change in the default PRT at some point. Thanks for your change.
Maybe you used XrmServiceToolkit library in the past?
Or you are still using it?
Be aware of this issue when retrieving data with FetchXml and LinkEntity aliases https://t.co/3svjwIhXyA
#MSDynCRM
@graceytech No. It was a regression in the documentation system. This error you saw was actually found and fixed last May, but the VS IntelliSense support XML for SDK assemblies is intertwined with the reference docs. If one is updated without the other, the change is overwritten.