hexagon logo

DataPage+ Saved Reports

It's probably not worth asking this, since Hexagon never gave a crap about DataPage anyways, but...

Why do my saved reports not stay saved as the report that I created? Randomly(?) the saved reports lose the label order, and when the report is applied, the labels on the first page are labels that should be on a later page, and the labels that should be on the first page are somewhere in the middle. What's the point of a saved report if you actually have to recreate it 50% of the time?
Parents
  • Hi ,

    I've been poking around and my saved reports are behaving well. Could I bug you for some extra detail to scope my testing;

    - Is this CAD / Text / Chart (or any)?
    - Is it a specific type of label (i.e. a run chart) that is getting lost or losing position?
    - Does it happen with the same user creating as recalling?
    - Is it losing the styling in datapage, or only in the exported report delivery service?


    Sorry about the questions - I know you said this was a bit random so I expect there isn't a simple answer we can just go fix. If I can get the problem duplicated, it'll be much easier to track down though.


    and , how dare you! I could fill the NSA's "metadata" servers with corrupt (unopenable) datapage RT databases. I don't miss those days at all.
  • I never EVER had any corrupt databases with DP/RT until I started using it for 2 machines. Simple fix was to put the database on the faster machine PC. ALL data from an old Validator using Pcdmis V3.7 and running on an XP box gets dumped to the new(er) Global using Pcdmis 2016 and running on Win7. DP/RT is on the XP pc, reading the database from the Win7 pc. When it was both going to the XP pc, I had issues until I moved the database. We've used DP/RT since the 3.5" floppy days and never had any corrupt databases, until the 2 machine set up 3 years ago.

    You just had to know how to clean out the database. Yes, takes a couple steps, but keep it clean, and no issues. Remember, deleting a part in DP/RT didn't delete any data, to do that, you had to delete the part(s) you no longer wanted on there, then do an ASCII data dump, then pull that into a new database. Takes about 10 minutes a couple times a year.
Reply
  • I never EVER had any corrupt databases with DP/RT until I started using it for 2 machines. Simple fix was to put the database on the faster machine PC. ALL data from an old Validator using Pcdmis V3.7 and running on an XP box gets dumped to the new(er) Global using Pcdmis 2016 and running on Win7. DP/RT is on the XP pc, reading the database from the Win7 pc. When it was both going to the XP pc, I had issues until I moved the database. We've used DP/RT since the 3.5" floppy days and never had any corrupt databases, until the 2 machine set up 3 years ago.

    You just had to know how to clean out the database. Yes, takes a couple steps, but keep it clean, and no issues. Remember, deleting a part in DP/RT didn't delete any data, to do that, you had to delete the part(s) you no longer wanted on there, then do an ASCII data dump, then pull that into a new database. Takes about 10 minutes a couple times a year.
Children
No Data