Archive
Table alias is not unique amongst all top-level table and join aliases – Exception
Recently we upgraded from UR 8 to UR 13 and from then I was getting ‘Unexpected’ error when I was adding members to my ‘Dynamic Marketing list’ using ‘Advanced Find’ window.
Below is the error log from my Event viewer
Exception type: CrmException
Exception message: Table alias a_7f4fc1baff99e111bef200155dc87c59 is not unique amongst all top-level table and join aliases
This is a known issue with UR 12 and would be resolved in UR 15.
Here is the link which has solution/workaround for the issue.
🙂
Show custom messages as banner notifications – CRM 2011
In CRM 2011, one way to show custom messages is using Jscript ‘alert’ function.
In one of our requirement we have to display a custom message on CRM form banner like OOB notification.
We can achieve this using Jscript, but it’s an unsupported way and there are no guarantees that this code won’t change in the future.
I am providing 2 scripts which is compatible Pre and Post UR 12.
Post UR 12
// Level – 1 (Critical), Level – 2 (Info), Level – 3 (Warning),
function addNotification(message, level) {
try {
var notificationsList = Sys.Application.findComponent(‘crmNotifications’);
if (notificationsList) {
notificationsList.AddNotification(‘noteId1’, level, ‘namespace’, message);
}
} catch (e) {
}
}
Pre UR 12
// Level – 1 (Critical), Level – 2 (Info), Level – 3 (Warning),
function addNotification(message, level) {
try {
var notificationsArea = document.getElementById(‘crmNotifications’);
if (notificationsArea) {
if (level == 1) { //critical
notificationsArea.AddNotification(‘mep1’, 1, ‘source’, message);
}
if (level == 2) { //Info
notificationsArea.AddNotification(‘mep3’, 3, ‘source’, message);
}
if (level == 3) { //Warning
notificationsArea.AddNotification(‘mep2’, 2, ‘source’, message);
}
if (message == “”) { // Clear the notifications
notificationsArea.SetNotifications(null, null);
}
}
} catch (e) {
}
}
How do I use the method
- To show custom message as Information, pass message and Level =2
addNotification(“This is sample message.”, 2);
Note – CRM 2013, has a new feature to display Notifications which is a supported way.
🙂
Lead qualify process design changes in UR 12 – CRM 2011
In UR 12, the lead conversion process has been redesigned. Refer below for lead qualify process before and after UR 12
Lead conversion before UR 12
- Before UR 12, we have “Qualify” button on Lead ribbon
- It opens a “Convert Lead” web page, which gives us options to create Contact/Account/Opportunity.
After UR 12
With new design, the “Convert Lead” dialog box no longer appears during lead qualification.
- We have 2 ribbon buttons (Qualify and Disqualify).
- The qualify button will automatically create the related Opportunity record based on the customer information entered into the Lead form
- Associated Contact and Account records will also be automatically created based on the First Name, Last Name, and Company Name field data, respectively
- If you click disqualify you are able to select the status reason, otherwise if you click qualify the lead will just automatically be qualified.
KB Article which talks about the same