Comments
Hi Mukti, did you find a solution for this?I am facing the same with cash advance workflow, when trying to validate "An error has occurred. Exception occurred while executing action validate on Entity WorkflowWorkItem: The RefTableId (5077) must refer to either TrvExpTable (16365) or TrvExpTrans (20447). Exception has been thrown by the target of an invocation."
This is a great suggestion. I'm working on revising our permissions sets ahead of the security group enforcement at the end of this month and my users have personalizations that I'd like to copy to new profiles as well. It would be so much easier and less time consuming if I could just export an individuals personalizations and import them into the new profile. Or when we get a new users in a department, copy the personalizations to them.
This is a bug.The standard retention policy fails because no more than 10,000 records can be deleted at once when using the standard job queue. The codeunit 3997 - Retention Policy JQ expects a confirmation with a simple "yes" or "no." However, no user interaction is possible. I believe the issue can be resolved by removing the confirmation (See green) , allowing the job queue to automatically proceed with deleting the next 10,000 records.Please check the code of the codeunit:if Confirm(confirmRerunMsg, true, MaxNumberOfRecordsToDelete()) then ContinueWithRerun := true;
This is a bug.The standard retention policy fails because no more than 10,000 records can be deleted at once when using the standard job queue. The codeunit 3997 - Retention Policy JQ expects a confirmation with a simple "yes" or "no." However, no user interaction is possible. I believe the issue can be resolved by removing the confirmation (See green) , allowing the job queue to automatically proceed with deleting the next 10,000 records.Please check the code of the codeunit:if Confirm(confirmRerunMsg, true, MaxNumberOfRecordsToDelete()) then ContinueWithRerun := true;
Hi @Adnan,Thank you for supporting this idea.The way I am thinking is not to change the behavior of the existing and / or operators we have already in BC.but to introduce new ones.For the and operator, that will be something like: && (as in most languages), AndAlso (as in VB.net) or and_then (as used in PASCAL)For the or operator, that will be something like: || (as in most languages), OrElse (as in VB.net) or or_else (as used in PASCAL).