I have a classic dashboard which is working (It makes the user select a job - mandatory parameter, selects Job Header then the Inspection tables).
I had it generate a Kinetic application just to test it out, which works.
I then exported the application and imported it into our Pilot environment with less data just so I could play with it.
Classic Application works, Kinetic does not.
I go back to the BAQ designer and the BAQ works in both the classic and kinetic designer. Not a surprise as it works in Live and we have less data in Pilot.
Makes me worried about all the items that I am converting in Pilot and testing to go live. Some of these just might refuse to work and I have no idea why.
I design in Pilot generally and move to live but this time I was looking at the dashboard and live and hit the generate Application button. It worked, it was one of the rare ones that I did not have to tweak and I exported it.
I went back into the Dashboard in Pilot and regenerated it and now it somehow works.
So exporting a functioning dashboard from one environment to another isn’t a guarantor of success? (The BAQ was already in both environments and working).
So what do we do when the Classic Dashboard interface is gone? Just hope this does not happen?
Stranger and stranger. I definitely call this an Alpha product.
If I export it should function.
It would be nice if you had the option to export it with the BAQS like Classic allows you to but going backwards in functionality seems to be the order of the day.
I can make a simple dashboard in minutes with the Classic interface complete with Tracker. There is no add Tracker option in the new interface (unless I missed it somehow) and now I can’t even count on an exported dashboard working. No error messages, no warnings. Just nothing.
I haven’t made a classic dashboard in a couple years, so I am rusty on this. But what exactly is your export process?
I found this from back in the day:
But I feel like that is not needed anymore.
Let me back up a bit.
If you make an “Application” in dev (from scratch; not from a classic dashboard), you can (depending on version) export the base app and export one or more layers (plus any needed BAQs/EFx of course) and import all of that into production without ever touching a classic dashboard interface.
OTOH, if the “Application” is a converted classic dashboard, well frankly I don’t know how those import over, whether you need to do additional steps.
But I assume not; once it is an Application, you should be good to export it as such with no trace that it was ever a classic dashboard.
