Hi all,
I am testing the amendment of assets and the Amendment Quote process worked well but when I tried to use the 'Create Order' button, I got this error
Error element Create_Orders_From_Quote (FlowActionCall).
refAppUsageAssignment0: duplicate value found: RecordId duplicates value on record with id: 0j8VF00000572YUYAY
That id seems to be linked to an AppUsageAssignment record. I'm using the standard Salesforce 'Create Orders From Quote' flow. The only place where I do anything with the Application Usage is when I reference the App Usage Type of RevenueLifecycleManagement in a flow to create Assets from Activated Orders. (pic below)
I don't know why there would be a duplicate AppUsageAssignment - maybe I created some kind of loop from creating the assets from orders and now the amendment process doesn't like trying to reference back to an already created asset with a new order? I thought using the standard Salesforce flow would help prevent errors with the amendment process.
Has anyone encountered this or have recommendations for how to get around the error? I'm worried trying to create something customized will really start messing with the standard functionality.
Thanks!
#Revenue Cloud
@harry drop @Olajide Otolorin -Prince
Ok, I'm still encountering the error and for every error message I'm getting a new refAppUsageAssignment record ID.. All of my Application Usage Types are 'RevenueLifecycleManagement' which is what all SF help documents say it should be.
I have a custom flow to create orders but it does not assign an Application Usage Type. All of my Quotes, Orders, Assets etc have Revenue Lifecycle Management as the Application Usage Type. I wouldn't think that having the assignment should mess with an Amendment Order being created.
Should I try adding a 'Get Records' for Application Usage Assignment so that the flow knows this is already created before it tries to say there is a duplicate? Or does a new AppUsage need to be created for amendments/renewals? If so, what is that? Because all I have seen is that it should be Revenue Lifecycle Management..
Thanks so much!!
