Hi SanfordYes, you are right. The case shows under Incident, under the "account".However, why I see "case" folder : I assume, cases should appear here ?Also, why I see the account name with a hug alphanumeric number append to it ? is it possible to see the exact name as it shows in CRM ?Thanks
Here is the link to the app. Again, I haven't tested this app with an online instance.
For the flow, you need to determine your trigger,Create a sharepoint folder using the name of the recordCreate a Dynamics 365 Document Location record with the regarding set to the triggering record and the relative URL set to the folder created in the previous step. The document location record is how Dynamics associates SharePoint folders.
I'll attempt to create a template and share in the near future.
I had to update the org db for another issue. I used this solution and it worked well. Goto releases to download the zipped managed solution file. Of course the command line app will not install a solution in your instance, so it is up to you which to use.
Hi Mayank,I'm not sure which change you're referring to, is this something you can provide a link to?
Barring what that change might be, our users are sharing files and syncing them to their desktops as well as making use of the versioning and collaboration tools that SP Online provides. Up to this point, those kinds of features seem require a lot of finagling to set up with Blob storage.Few are actually going to SharePoint online but they all need the 'Dropbox' like desktop syncing.Best of luck with the migration,Chris
Thanks for the information. Many companies continue to use the SharePoint integration for the reasons you listed. Mainly as a document repository for collaboration. The updated storage capacity allows for more data being generated and stored. Which can then be used to provide better analytics for example with Power Bi. With the new storage capacity, we can create more robust apps to capture data and refine reports to show the data. Documents and other attachments used in a collaborative fashion should be stored elsewhere. Again, the records created in the CDS will be used for analysis or something similar.
Of course this is all based on the requirements of the Company and project. For example, we have a Site Visit app which stores photos of the site in SharePoint to be used by 3rd party team during installation of the product.
I hope this helps with "Why still use SharePoint?"
If you've found this thread useful, dive deeper into User Group community content by role