DBohner-(db)
Legendary Poster
and... tomorrow is coming....
I'm working through an issue were a report that was working in Production - has suddenly gone haywire.
Recently I was asked the make the PDF a little wider, so all columns would fit on a report. I changed the Print Properties of the report and versions and pushed forward to Production.
The Financial Report Level-Breaks on OBJ, only.
- When tested in DV - all looked great
- When tested in PY - all looked great
- When run in Production - all-holy-hades-grenades happened. The Sequencing/Level break is way haywire... It acts like it's level-breaking on company.obj.sub or worse... Object.Subs are displaying and not in any specific order.
We refreshed PD Data to the lower environments - and the report still looks and behaves in the lower environments.
We have pushed the objects through the promotion cycles - several times, and the only place the report is bonkers - is Production.
I'm out of ideas... Standard Financial BSVW and fairly standard financial report...
Thoughts???
(db)
I'm working through an issue were a report that was working in Production - has suddenly gone haywire.
Recently I was asked the make the PDF a little wider, so all columns would fit on a report. I changed the Print Properties of the report and versions and pushed forward to Production.
The Financial Report Level-Breaks on OBJ, only.
- When tested in DV - all looked great
- When tested in PY - all looked great
- When run in Production - all-holy-hades-grenades happened. The Sequencing/Level break is way haywire... It acts like it's level-breaking on company.obj.sub or worse... Object.Subs are displaying and not in any specific order.
We refreshed PD Data to the lower environments - and the report still looks and behaves in the lower environments.
We have pushed the objects through the promotion cycles - several times, and the only place the report is bonkers - is Production.
I'm out of ideas... Standard Financial BSVW and fairly standard financial report...
Thoughts???
(db)