You’re offline. This is a read only version of the page.
I'm seeing some issues as customisations of a report have been promoted from the Development environment to the Test environment, as the custom table that underlies the report (InvoiceReportTmp) was inadvertently left as a Regular table during the promotion. Initially this meant each instance of the report used the same data: quickly spotted, table type changed in Test, full compile of project & incremental CIL compile completed, with XPPIL folder cleared down before an AOS restart. Test is now in a state whereby report generation intermittently throws the error "Invalid object name dbo.InvoiceReportTmp" when running an insert statement.
I think the simple solution is probably to take a new export of the customisations model from the Dev environment and load into Test, but the fact that the error is intermittent has me pretty confused. Can anyone please advise whether there's something else I've missed in the attempt to rectify the problem? Changing the table type from Regular to TempDB in Dev and running the report without a project & CIL compile gives me a reliable error, with the error reliably not occurring following the project & CIL compile, so I'm not able to reproduce the state of the Test environment.
*This post is locked for comments
I have the same question (0)
Seems the issue was down to cached CIL on one or more of the AOS servers in the Test environment: once a colleague pointed out that there was more than one AOS service to restart, a simple restart alone was enough (XPPIL appeared to be refreshed from the model store on restart).
Redeploying the model or the project may not have done the job if I hadn't known to restart multiple servers...
Share
Report
All responses (
Answers (
4
