Hi -

I'm trying to create a method that will automatically create something I can save and use later, which will let me automate data migration from one version of a class to the next.

When I compile a normal persistent class, a "storage" gets created, and I would like to be able to archive some code that would let me recreate this "old storage" so I could access an "older version" from a global and map the values into the current mapping of the class.

Hi -

I was looking at the “Purge Data Management” page, and one of the “Record Types” is the “I/O Log” which sometimes doesn’t clear when you purge all of the message.

But I’m not sure what it’s actually reporting as “I/O Log” messages (and I can’t find anyplace to view what is being considered I/O Logged Messages - so I can understand what’s happening)

Can anyone shed some light on these messages?

Hi -

I need an example of what I need to "map" to have a common dashboard defined so it will visible/usable in multiple namespaces.

I have created a dashboard in "SAMPLES" (namespace and database) and I would like to have this dashboard be accessable/useable from a 2nd namespace, but I'm not having any success in doing mappings (global/package/routine/data) to be able to get DeepSee to be able to see/display the dashboard.

What is the minimum that I need to map?

Hi -

If you have Cache installed on a Cent OS machine, and you want to switch the OS to Red Hat 7, and your Caché is installed on a non-OS drive, do you need to reinstall Caché?

I don't think so, but I wanted to check

Hello DeepSee'ers -

How hard is it to brand a dashboard to a login?

The situation is, I have a Partner that is looking to create common Dashboards in a SaaS model where the Partner's Clients would want to have their individual views of this common dashbaord be branded (logos, color, styles, etc.) to match the Client's branding. This my Partner's Client's End Users will see this common dashboard as the dashboard from the "Client" and not the "Partner" (and certainly not ISC branding)

ie.  ISC -> Partner -> Client -> End User