A place to ask questions, connect with others, and stay in the know
We went back to the original versions of the clients and ran the imports again. The errors mentioned above still occur but the job finishes in a reasonable amount of time and all the data loads properly.When running with the Itemization Balance table mapped, we had our SQL server admin team take a look to see what they see running and they came back to us and said they see the job running the UPDATE ib (Itemization Balance update) during the new business. This really shouldn't be running since it's not adding financial transactions. Even still, that shouldn't take that long. However, after some digging I found two different triggers for the IB update. One is attached to the IB table and the other is attached to the Payhistory table. (screenshots attached)Should there be two triggers?Is anyone else reporting issues with the schema files?Is anyone else reporting super long processing times?It appears that without updating the clients, everything runs fines with the exception of those 3 errors mentioned above. It's just without the client update, nothing gets mapped to the itemization balance and itemization date unless we go back around and run a SQL update for it.
Every year, Genesys® delivers more than 70 billion remarkable customer experiences for organizations in over 100 countries. Through the power of the cloud and AI, our technology connects every customer moment across marketing, sales and service on any channel, while also improving employee experiences. Genesys pioneered Experience as a ServiceSM so organizations of any size can provide true personalization at scale, interact with empathy, and foster customer trust and loyalty. This is enabled by Genesys Cloud™, an all-in-one solution and the world's leading public cloud contact center platform, designed for rapid innovation, scalability and flexibility. Visit www.genesys.com.