We were recently getting the below error in one of the views in the Dashboard.
0x90000010 Can not retrieve view’s metadata
The issue occurred because we had converted that Dashboard from a personal to System / Public Dashboard using the below wonderful XrmToolbox Plugin, https://www.xrmtoolbox.com/plugins/Carfup.XTBPlugins.PersonalViewsMigration/, which converted it to System Dashboard successfully, however, this was one of the personal views inside that dashboard.
So we converted that personal view to the system view (using the same tool) and then updated the Dashboard to refer to the converted system view, which fixed the issue.
Recently in one of our custom pages, we had to set the default value (DefaultSelectedItems) of the combo box based on one of the lookup fields on the record. We were opening the custom page from the ribbon button on the form.
Below is our function to pass the record’s GUID to the custom page from the button.
openSearchCustomPage: function (primaryControl, firstPrimaryItemId) {
var pageInputCustom = {
pageType: 'custom',
name: 'custom_searchproduct_570ed',
entityName: 'lead',
recordId: firstPrimaryItemId
};
var navigationOptions = {
target: 2,
position: 1,
width: 1350
};
Xrm.Navigation.navigateTo(pageInputCustom, navigationOptions).then(
function success(result) {
console.log(result);
},
function error(error) {
console.log(error);
}
);
}
Next in App’s OnStart, we are setting the GUID of the record to a variable first, and than setting another variable to store the GUID of the Region lookup field on that record.
// text variable passed by the form / webresource/ ribbon
Set(varEnquiryIdWithoutCurlyBraces,GUID(Substitute(Substitute(Param("recordId"),"{",""),"}","")));
// get the Region Of Interest from the Lead / Enquiry ID
// If value present use it for prefiltering the Gallery Items
Set(varRegionOfInterest,LookUp(Enquiries,Lead=varEnquiryIdWithoutCurlyBraces, 'Region of Interest'));
And lastly, for the combo box (Items = Region (custom table)), we are setting the DefaultSelectedItems as follows
LookUp(Regions,Region=varRegionOfInterest.Region)
We also tried using the Filter option, but it was giving incorrect values.
The value on the form –
The value in the Custom Page –
Correct value populated for combo box Region, and incorrect for the one using Filter formula
A common problem that many users report in CRM is that the system is automatically sending out e-mail notifications to recipients for CRM Appointments without the user’s permission. However, you know CRM doesn’t automatically send out Appointment e-mails and there are no background processes or workflows that are sending these notifications. So what are the users referring to?
Since CRM 2013, most users have been creating appointments through the Social Pane. One nice thing about creating appointments from the Social Pane is that CRM automatically populates information onto the Appointment form. A major downside to this though is that one of the fields that gets populated is the “Required” field.
When an Appointment is saved with values in the “Required” field and it syncs to a user’s e-mail, it has the same effect as inviting attendees to an appointment in Outlook or Office 365. When attendees are on an Appointment, e-mail notifications are sent out…
We were getting this error in the submission of one of our outbound Marketing forms.
Activity id: e1ede147-efb6-457d-bc19-826c6176a2e4, Request id: jH7xRiEzGFTdZQTbE2fkh9_Z_WtjumCqJERuYZbGSL0_0, Exception: Entity ‘Contact’ With Id = 896b960d-c5d7-4c4d-95c7-a9e226afbf8e Does Not Exist
The form had only the Lead form matching defined and Only leads for Update contacts / leads.
So here because of some earlier multiple/different form submissions, a contact got created and stored in the browser’s cookie, which CRM was referring to, and trying to set a Parent Contact for the lead record even though we were having Only leads set for update contact/leads option.
While trying to import the solution (patch), we were getting the below error.
“Expected non-empty Guid”
There was hardly any detail in the log file also
We tried removing the solution component one by one in our source environment and trying the import again in the target environment.
Eventually removing the Pages (custom page) allowed us to import the solution successfully into the target environment.
We then compared the customization.xml of the current solution with the backup solution of the Target and see the information missing in the current solution.
Left is – Current solution (giving error) and Right is the backup solution of the target.
Interestingly next time when we extracted the new patch after a couple of days, we could see the tag there and so no issues that time.