Allow content renaming on import

Alex trehubenko shared this idea 21 months ago
Idea Logged

We prefer to maintain two instances of each piece of content, one using our production database connection, which has more complete data for users, and then second using our test connection which we use to prepare for DB changes ahead of time.

We currently do this by exporting content, importing it back, and changing the connection source and name. Adding the ability to rename reports on import would facilitate this process. We rename so that it is apparent which version of the content is the test report and which is the production.

Replies (1)


Hello Alex,

I have created this Idea in the community so that we can track it and for other Yellowfin customers to find and comment on. I have also submitted it to the product team. Hopefully we will see it added in future release.

Have a great day,


Leave a Comment
Attach a file