Skip to main content

SSRS reports for activity feeds

SSRS reports for activity feeds

Usually I prefer to create my SSRS reports based on SQL datasets. But sometimes there are situations, where this is not possible and you have to go for datasets based on FetchXML.


Now I faced such a situation, since I have been asked to generate a report displaying the latest post date (and additional other details) of each account.


But for the "post" entity no FilteredView exists:




The post entity contains the following attributes:



So on the one hand a post can be directly linked to an account via the regardingobjectid field.


But what about posts about an appointment or opportunity regarding an account. Here the "postrole" entity comes into place.


The postrole entity contains references to all entities that are related to one post, e.g. in case of a post regarding an opportunity there could be references to the systemuser, the opportunity and the account/contact:






So in case you want to retrieve all accounts and the latest update date of all posts regarding that accounts, you could use the following FetchXML statement:




This statement only returns the accountid and the lastupdate date. So in case you have to add additional information, you need to extend it.


In my case I had to provide other details like account name, manager, last meeting, next meeting, a.s.o. So I created a second dataset (based on SQL) and linked the datasets in a table via a lookup.


Hope this helps ;)
Thomas

Comments

Popular posts from this blog

Power Automate Get absolute Sharepoint URL from document location

Document Locations If you enable Sharepoint document integration in your model driven apps, you can define for which entities the possibility to upload documents to sharepoint shall be offered and you can define a folder structure. Possible folder structures can either be based on account or contact, which means if you create child items (e.g. opportunities, activities, ...) sub folders are created below. If an entity is enabled for document management a "Files" tab is added to the form of your model driven app and as soon as you click on that tab a folder is automatically generated on Sharepoint. Once the folder has been created you have options to create new or upload existing file or to open the document location (folder) on Sharepoint: What happens behind the scenes is, as soon as you click on the files tab your model driven app checks, weither a "document location" for this item already exists, or not. The document location is an own entity in C

Send e-mails with a link to the record via Power Automate

Today we gonna have a look at how to send an e-mail with a link to a CDS record via Power Automate. In the good old classic workflows, you could directly reference the "record URL" from the dynamic data. But since UCI has been launched and you have the possiblity to target different apps, you already had to do a few more steps in the classic workflows as well. The URL to a CDS record consists of multiple things: CRM URL appid entity name record id So we will work this out one after the other. First we add a "List record" action to lookup the appid of the app, we target. We look for "model driven apps" and filter by the name of the app: Then we initialize a variable with the resulting app id: Then we initialize another variable and extract the CRM_URL: Then we fetch our records, where we want to send out a notification with a link, in this case we look for workorders fullfilling certain criteria: Now we compose the record URL: As a next step we create a new

Working with Optionset lables in Power Automate

Connector Types Power Automate currently offers 3 different connectors, to connect Power Automate with your Dynamics 365 instance: Dynamics 365 Common Data Service Common Data Service (current environment) Today we will look on ways how to retrieve option set labels via the different connectors, for our sample accounts: Dynamics 365 This connector should not be used any more , since in April 2019 it has been announced as being deprecated. https://flow.microsoft.com/en-us/blog/nine-new-connectors-in-april-and-improved-visibility-into-trigger-failures/ With the Dynamics 365 connector it was quite easy to work with optionsets, since it offered both the optionset value (int) and the optionset label (name) in the dynamic content: And here we go, these are our results: Common Data Service Since the Dynamics 365 connector has been deprecated, this is the connector you should use. If you perform a "Get record" or "List records&