Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We just upgraded our development environment to 2022.05 SP 15. The "Adding updated rows for Full History objects to dimension" steps in the data mart processing of SCD2 dimensions does not include the VID column in the insert statement, which violates the non-null constraint on the tables, so processing always fails.
How does something like this get overlooked in QA testing?
Hello @jtompkins
You've opened a support ticket for with us and will continue to work in the ticket.
Regards,
Suresh
Still completely mind-boggling and frustrating how something as obvious as a primary key constraint gets overlooked in a release.