Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I am encountering a strange problem with CRM 2011 that should not be happening.
I have an SSRS Report with the following query:
SELECT new_s_batchmanagementid [BatchID]
FROM filterednew_s_batchmanagement AS CRMAF_filterednew_s_batchmanagement
My understanding is that this query is supposed retrieve the GUID for the specific record that is opened in the form where this report is run from.
My expectation is that when I run this report from within the new_s_batchmanagement form on a specific new_s_batchmanagement record, I will get back the GUID of the record in which I am running it.
The specific record shown below, has a GUID of 59CA9DB0-5CD7-E611-AE66-000C29D70C71 - that is what I expect to get back
However, I don't get that back and instead I get back the GUID that corresponds to the very first new_s_batchmanagement record I entered in CRM whose GUID is B5830132-88D6-E611-9362-000C29D70C71
This is a problem because I am unable to run a report on the currently open record if I cannot even get the GUID for that currently open record.
I have never experienced this issue before, so clearly something is terribly wrong.
My other reports that do get the GUID for the currently open record look identical to this.
I set this up so it is related to Forms for related record types as shown below.
I don't understand why this one is getting the first entered GUID instead of the GUID for the current record from where the report is being run.
The only thing that's changed since I last wrote something like this is that hundreds of Windows Server, SQL, and CRM Updates and Service Packs have been applied.
Any help would be greatly appreciated.
I got around the issue by using a parent/child report and sub-report. That works as expected.
Business Applications communities