Thanks Microsoft for this recognition and thanks to all the wonderful and passionate Dynamics 365 (CRM) professionals who have inspired and motivated me and others for several years, to keep learning and contributing in the community and to grow in the process!
Kindly refer the previous post, here we will be adding style to the component created in the post.
Let us continue with our previous sample component and try adding style to it.
Hope it helps..
Update – use context instead of Xrm.Page
Also,
https://nishantrana.me/2020/01/20/best-resources-to-start-with-power-apps-code-component-pcf/
Go through below articles to get a better understanding
Below is the quick step by step guide to get started (sort of Hello World example)
pac pcf init
– -namespace <namespace for the component>
– -name <name of the component>
– -template <component type>
It adds the following files in the folder.
*Use ctrl + c è to terminate the job.
pac solution init – -publisherName [publisher name] – -customizationPrefix [publisher prefix]
pac solution add-reference – -path [path to pcfproj file]
i.e. reference of the below path.
For reference à
Followed by
1. Install npm
2. Install PowerApps CLI
3. Install Visual Studio 2017 or later
4. Create a new folder for the project.
5. Navigate to the folder in Developer Command Prompt and run the following command to create the component project
6. Install the project dependencies using below command
7. Update ControlManifest.Input.xml
8. Update index.ts
9. Build the project
10. Use the below command to test the component
11. Create a folder for holding the solution zip and related files. Navigate to that folder and run the below command.
12. Add reference of the custom component in the solution
13. To create the Solution Zip File
14. Import the solution file and use it inside Dynamics 365 CE.
Hope it helps..
Few months back I wrote about the features of the new model drive form designer in PowerApps.
There are few improvements done in it since then
For e.g.
Phone field:
Address Section:
However still there are few important features missing when compared to our classic form designer like
The new model driven form designer looks promising, however we’d have to wait a bit more, before it can have all the expected (or some new) features added to it.
Hope it helps..
Recently in one of our environments, we started getting the issue that all our workflows were getting stuck at “Waiting for resources”.
As usual first step was to check if Microsoft Dynamics 365 Asynchronous Processing Service is running it or not.
The service was disabled, so we enabled it. But still, it didn’t fix the issue.
Next thing we tried was as suggested in the below article
https://www.powerobjects.com/blog/2013/03/28/how-to-fix-a-crm-workflow-stuck-in-progress/
The value for AsyncSdkRootDomain was blank which we updated followed by a restart of the service. Still no luck.
Eventually, we came to know that Servers setting for the roles Full Server were in the disabled state inside the Deployment Manager for the organization.
The reason CRM was still working because these services (including IIS Web Site) were already manually started earlier, however, the status was still disabled for this setting within Deployment Manager. (These settings were done by the network team who were planning to create the replica of these machines, and they wanted to disable the applications and our CRM technical team was unaware of it.)
Enabling it fixed the issue for it.
Hope it helps..
Recently I had written an article for Nigel Frank that list down step by step process of using XML Source Component of KingswaySoft for integration with Dynamics 365 CE
https://www.nigelfrank.com/blog/integrate-dynamics-365-for-customer-engagement-with-xml/
We have used XML Source Component to read the XML files.
The packages that we developed were running fine from Visual Studio SSDT but on deployment for one of our package that was using Script Component we were getting the below error while running from within SQL.
After a lot of debugging and spending a good amount of time to figure out the issue, we realized that the value of one of the input columns was not being passed to Script Component from XML Source component i.e. _ParentKeyField
This is a special column which XML Source Component adds for the child records through which we can associate it to the parent record.
This happens when we are running it from SQL and only for the Script Component. This worked fine while running it from within SSDT and in other packages even from SQL when we weren’t using Script Component.
As a quick fix, we applied XLST Transformation to put the same tag for the child records also and to refer that instead of _ParentKeyField
In parallel, we also asked the same question to the KingswaySoft Support team (info@kingswaysoft.com)
One thing I would like to explicitly mention is that KingswaySoft support team is one of the best out there, not only you will get the response immediately, but also their team is very knowledgeable.
Below is the response we got
As suggested after setting the RunInOptimizedMode property to False for the Data Flow components the issue got fixed.
This property indicates whether the Data Flow task runs in optimized mode (RunInOptimizedMode property). Optimized mode improves performance by removing unused columns, outputs, and components from the data flow.
Hope it helps..
Nishant Rana's Weblog 