Posts

Pick and Removing Can't be processed at the same time. To pick this queue item, please unselect the option for removal.

Image
Scenario At my work, I was assigned a task to automatically route the case to a queue member who is currently assigned fewer cases.  Development was completed and after detailed unit testing, it was released to UAT for QA to execute their test cases. It worked absolutely fine on the first day of QA. But, stopped working all of sudden. Problem Statement The cases stopped routing automatically to the queue member.  Also, when manually picking the queue item from the queue and selecting remove from the queue to YES, the below error was popping up. Solution So after spending hours on the internet to find out the reason behind it. We couldn't find any solution. However,  while doing a comparison between queues available in DEV and UAT, we find out that someone enabled "Automatic Work Distribution" (AWD) in queues available at UAT. Which is specifically for Omni Channel and that was stopping to remove the queue item as soon as it is picked up by someone. So as soon as we disabl
Post a Comment
Read more

How to show missing buttons in UCI interface

Image
Problem In new interface of Dynamics CRM certain button on ribbon might not available. For example, Qualify button on Leads form or Add Existing button on subgrid ribbon.  Solution Add entity meta data to a solution, say, LeadsRibbon Open solution in ribbon workbench On form ribbon of Leads, right click on Qualify button and select Customize Command Under Enable Rule section of the command remove below highlighted rule Publish solution Cheers!!!!
Post a Comment
Read more

Exception handling in Power Automate Flows

Image
Out of other errors type one is logical errors. There are many reasons for this type of errors, for example, unexpected user input etc. In most of computer languages we handle these error by exception handling or try-catch blocks. However, in Power Automate we also have this feature available to handle exceptions well in the flow and keep the flow running to complete rest of the flow logic. There are two ways to implement exception handling in Power Automate Flows.  Use Power Automate template (https://emea.flow.microsoft.com/en-us/galleries/public/templates/e8e028c6df7b4eb786abdf510e4f1da3/try-catch-and-finally-template/) Using 'Scope' action with 'Configure Run After'  property Let's dig into each block in the template Try - Contain all the actions coming from main flow Catch - This control configured to run once "Try" block is failed Finally - This block must run, no matter what is the output of previous block Now lets configure Try-Catch blocks within
Post a Comment
Read more

Get Lookup / Power Automate text value instead of guid / integer values using Power Automate

Image
Problem Statement In Power Automate flows, I was getting GUID for lookup and integer for optionset fields instead of text values for both fields.  Example For a contact records below from CRM, I've Account Name as lookup field and Preferred Method of Contact an optionset field. Solution To get face values for lookup as well as for optionset, you need to use below expressions body('SourceDataSet')?['<FieldName>@OData.Community.Display.V1.FormattedValue'] SourceDataSet - the dataset from where you are trying to get face values for optionset and lookup Field Name - logical field name;  In our case, source data set is "GetContact" while below are fields Preferred Method of Contact - preferredcontactmethodcode Account Name (lookup field) - _parentcustomerid_value So as par above expression, let complete our expression and put in Power Automate Flows Compose component. For Optionset,  body('GetContact')?['preferredcontactmethodcode@OData.Commun
Post a Comment
Read more