Microsoft Dynamics 365 – Page 165 – Nishant Rana's Weblog

Scribe Insight Limitation – XML Source doesn’t support repeating sibling nodes

Recently we were evaluating Scribe Insight as our Integration tool for one of our clients. The requirement was to read an xml and create records in Dynamics 365 CE.

The basic structure was something like below, with Account as the parent tag and Payment, Assets, Consumer as repeating child nodes of Account i.e. 1 – n.

However, to our surprise when we started defining the same structure in the XML Component within Scribe Workbench we got the below error message à

—————————

XML Component

—————————

Repeating nodes are not supported for cousins, siblings, etc. Multiple repeating nodes must be related linearly to repeating nodes that already exist. Thus, a new repeating node must be a grandparent, parent, child, grandchild, etc., to an existing repeating node.

—————————

Interestingly enough the same limitation doesn’t exist in Scribe Online. Had posted something similar few days’ back on that

https://nishantrana.me/2019/01/14/scribe-online-working-with-hierarchical-data-in-dynamics-365-ce/

As we wanted to go with something that works in On Premise setup we went ahead with SSIS Productivity Pack of KingswaySoft https://www.kingswaysoft.com/products/ssis-productivity-pack which had XML components that works perfectly well with this kind of schema or structure.

Hope it helps..

contextUserId is missing privilege ae5c41f0-e823-4cb9-b25a-8ef020201973 error in WebAPI

We were getting the below error while using impersonation in our WebAPI

2019-02-26_1044

Searching for the privilege id we got the following detail

{“@odata.etag”:”W/\”47875405\””,”overwritetime”:”1900-01-01T00:00:00Z”,”solutionid”:”fd140aad-4df4-11dd-bd17-0019b9312238″,”introducedversion”:”8.2.0.0″,”canbebasic”:false,”canbedeep”:false,”ismanaged”:false,”accessright”:32,”canbeglobal”:true,”privilegeid”:”ae5c41f0-e823-4cb9-b25a-8ef020201973″,”canbeentityreference”:false,”privilegerowid”:”1b218262-afac-4859-b9e0-c8c0f6550231″,”componentstate”:0,”canbelocal”:false,”versionnumber”:47875405,”canbeparententityreference”:false,”name”:”prvActOnBehalfOfAnotherUser“},

So the user was missing the Act On Behalf Of Another User privilege

https://nishantrana.me/2018/01/30/user-does-not-have-the-privilege-to-act-on-behalf-another-user-error-while-using-impersonation-in-web-api-in-dynamics-365/

Hope it helps..

{Advanced Customization}10 Tips to design CRM Views like a Pro

Nice tips !

MSDYNAMICSBLOG BY DEEPESH

Here are a set of 10 Tips to design CRM Views like a Pro:

Try to limit the number of columns on the View and limit the number of scrolls that are required to be done on the View. Usually, end users do not like to scroll more than 2 times even on the Web client. Also, more the number of columns, slower the view will load as it has performance implications.
In case views show All Records then out of box status field (Active/Inactive) makes sense to be put on the View. As an example, for “Active Accounts does not make sense to show status field since this is self-explanatory and applied at the filter level itself. The column space can be saved to add another relevant column.
Place generic fields such as Created On/ Modified On, Created By/Modified by towards the end of your View column definition. This…

View original post 317 more words

Filter, Search, and Lookup functions in PowerApps compared.

Very informative !

Olena's Dynamics Blog (post-AI)

These are functions to find one or more records in a table.

	Matches by a formula or a single string *	*Multiple formulas accepted*	*Returns multiple* *records or a single record*	*Returns the subset of the original dataset or one value*	*No record found*	*Function to check if no record found*
*Filter*	Formula	Yes	Multiple	Subset	Empty table	IsEmpty
*Search*	String	No	Multiple	Subset	Empty table	IsEmpty
*Lookup*	Formula	No	First Single	One value	Blank	IsBlank

*The formula is evaluated for each record of the table. Records that result in true are included in the result. Besides the normal formula operators, you can use the in and exactinoperators for substring matches.

Fields of the record currently being processed are available within the formula. You simply reference them by name as you would any other value. You can also reference control properties and other values from throughout your…

View original post 287 more words

Scribe Online – Working with Upsert Block in Dynamics 365 CE

Continuing our previous posts on Scribe Online, let us look at the Upsert block for Dynamics 365 CRM Connector.

The way it works is à

The Upsert block will have a field called alternatekeyname where we need to provide the name of the alternate key as shown below.

In CRM à

Along with passing the value for the field(s) involved in the alternate key.

The way to achieve the same in Informatica Cloud

https://nishantrana.me/2018/05/18/using-alternate-key-to-upsertupdate-using-dynamics-365-for-sales-connector-of-infomatica-cloud/

Do check out this wonderful article that explains the usage of Upsert Block, Custome Update + Insert and Update/Insert block.

https://www.scribesoft.com/blog/2014/11/updateinsert/

Hope it helps..

D365: Dynamics 365 Developer Toolkit for VS 2017

Ajit Patra

Dynamics 365 Developer toolkit for Visual Studio 2017 can be installed by following the below steps:

Download Dynamics 365 Developer Toolkit for VS 2015 from here.
Once it is downloaded, extract the content of it to a folder
Open the folder to which the content has been extracted and open the file “extension.vsixmanifest” in a notepad or text editor.
Change the version number number from 14.0 to 15.0 as highlighted below and save the file:
After changing, it looks like below:
Select all the content in the extracted folder (from Step 2 above) and zip it
Rename the file to a [unique name].vsix and save it. Click Yes on Rename pop up.
Double click on the vsix file created in the step above and click on Install.
It’ll show a warning for incompatibility with VS 2017. Click on Yes and Proceed.
Installation will be started for VS 2017.