Thanks @Laura02 , I did think of this option, but since it was working with restriction on in 2019R1 I didn’t bother to try. Probably in the upgraded version changes might have been done to enforce this restriction.Anyways thanks a lot..
Thanks all, Issue was with our customized workflows for opportunities.
@Laura02 , thanks I will have a look..
any thoughts on why the same works on 2019 , but not on 2022R1 version?
Hi @Naveen Boga , that is correct.
same steps worked for us in the previous version 2019 R1, currently we have the upgraded version 2022R1.
For testing the approval maps are working as expected created only one step. If the quote meets the above rule actions and conditions, it should be auto approved. It doesn’t happen in my case, any thoughts or suggestions on what I might be missing?
@meganfriesen37 , thanks for reply and sharing the details. I did try the above for auto approval, I can see the approval getting triggered, but the issue is even after the quote is approved the status of the quote doesn’t change. It still remains in open status I was expecting the quote to be in Approved status.Secondly there are scenarios were the user who is submitting the Quote, can auto approve the quote without any approval. How can we achieve this?
Any help will be greatly appreciated.
Any thoughts?
@Shawn Burt , sorry for late response. I’m specifically looking to call the below methodsthis is our previous implementation CCPaymentEntry ccPaymentEntry = new CCPaymentEntry(aProcessingGraph);aProcessingGraph → this is ARPaymentCCProcessing graph //ccPaymentEntry.AddAfterProcessCallback(new AfterTranProcDelegate(ARPaymentEntry.PaymentTransaction.UpdateARPaymentAndSetWarning)); //ccPaymentEntry.AddAfterProcessCallback(new AfterTranProcDelegate(PaymentTransactionGraph<ARPaymentCCProcessing, ARPayment>.ReleaseARDocument));//ccPaymentEntry.AddAfterProcessCallback(new AfterTranProcDelegate(PaymentTransactionGraph<ARPaymentCCProcessing, ARPayment>.CheckForHeldForReviewStatusAfterProc)); not sure how can we do this in the upgraded version...
Hi @kandybeatty49 , sorry I missed out to mention. Yes it's a customized screen.This used to work in the previous version, so unsure what has changed in the upgrade.
Hi @Naveen Boga , sure. Attached.
thanks all, issue resolved....
I was referring to CRCase.MajorStatus , this field is obsolete now.
tried on the 2020 code version, no luck
@manikantad18 , We are in the process of upgrading from 2020 to 2022. For one of our customizations when adding reference to the latest dll’s and building customization project on VS we get the above compile time error for CRCase , this is a DAC under namespace PX.Objects.CR, looks like the field majorStatus is longer available under CRCase. Was checking if there is an alternate field that I can use or just ignore this field for now as it’s not available in the 2022 R1 version...
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.