Can I edit views from within the yellowfin db?

Jonas De Beukelaer shared this question 5 months ago
Answered

Hey,

We have quite a few orgs we work with at the moment. They should all have a similar setup, but I've noticed that they've diverged a lot recently.

I'd like to be able to, for example, more easily copy over field names and descriptions, from one org to the other. I'm hoping there's a way to do this via the db, so that I can write some SQL to copy over properties, instead of doing this through the ui, which would be very time consuming.

Is this possible?

Cheers,


Jonass

Comments (4)

photo
1

Hi Jonas,

If the changes are pretty uniform, your best luck here is to use the importer to replace entire views. While it is possible to edit definitions through the configuration database, I am hesitant to suggest this as view level changes propagate so heavily through out the program.

Sorry for the inconvenience.

Regards,

Nathan

photo
1

Hey Nathan,

Thanks for the info. I decided against doing that in the end. However, I've learn my lesson that I should always backup everything before copying views from one org to another –

After copying over, a metric (available in both views, the old and the new) was removed from all reports after replacing the view. Re-replacing with the old view did not recover the reports. I had to go through and re-add that metric, and all advanced functions using that metric, back in manually for all reports. I guess this is the kind of thing I was hoping to avoid by editing the db...

I don't know if this a known issue but it's certainly not ideal.

Thanks,

Jonas

photo
1

Hi Jonas,

Generally, we do suggest backing up your configuration database at least weekly just in case (and before any major changes)... sounds like you learned the hard way, sorry :/

Unfortunately the links in the configuration are quite complex when it comes to views so just rest assured that you would probably still be working through problems had you taken that approach.

Regarding the lost metric, if you notice warnings on import that say "field missing" I would recommend importing only the view first, validating it to make sure that all of the columns are there, and then importing reports on top of the repaired view so that they can successfully match all columns.

None the less, glad to hear that it is up and running. Let me know if there is anything else I can do to help here.

Nathan

photo
1

Hey,

Thanks for the tips. That's all from me for now.

Cheers,

Jonas