10-30-2018, 02:59 PM
execute it again
this is happening recently when the same changesets installs a new module and then directly tries to create a record for it. I think it is due to some of the recent cache optimizations we have made, the creation doesn't recognize the new module and fails. If you execute the changeset again it should create the record for you.
Let me know how it goes.
this is happening recently when the same changesets installs a new module and then directly tries to create a record for it. I think it is due to some of the recent cache optimizations we have made, the creation doesn't recognize the new module and fails. If you execute the changeset again it should create the record for you.
Let me know how it goes.
Joe
TSolucio
TSolucio