Export Content

Jasper Dan Estareja shared this problem 40 days ago
Resolved

Hi Support,


We are migrating one of our clients to a different Yellowfin instance. It seems like the Export functionality includes even the deleted contents. I get errors like:

- This content has changed. Please remove it and add the updated version to the Export List.

- Could not find the report with id 2836967.

I tried looking into the configdb table reportheader to find this 2836967 report, and the reportstatudecode is "deleted".


Is there another way we can export the contents from this instance? This is a multi-tenant server so we can't just export the entire configdb.


Hope you can assist us on this.


Thanks,


Jasper

Comments (5)

photo
1

Hi Jasper,


Thanks for reaching out.


I don't think we have any other recommended way to export content.

Could you please help me with the following:


1. /info.jsp to understand the exact build and environment details. You can append /info.jsp to the YF URL you are using or can export from the Administration -->System Administration

2. When did the issue start to occur (When was the last time it exported without any issue?) What has changed since then?

-Could not find report with id:

3. Does every report export throw this error ? or only reports that have associated content? (May be parent-child reports? )

4. Can we also check the reportassociate table for the id?

- This content has changed. Please remove it and add the updated version to the Export List.

5. Are we trying to export private content?

If so please refer to this article for information on how to proceed: https://community.yellowfinbi.com/knowledge-base/article/how-do-i-export-and-import-private-reports But it seems to be fixed in versions 8.0.12 and 9.7.3 or above.


Thanks,

Deepak

photo
1

Hi Deepak,

Regarding your questions:

1. Attached is the sysinfo.

2. We only noticed this happening just last week when we're trying to export.

3. It was weird that the alert was "could not find report with id", when I checked these reports in configdb, they actually have a Deleted reportstatuscode. Just for us to proceed with the export, I've set the reportstatuscode to Open.

4. These reports are in the reportassociate table.

1d79fb041276854e4308e43d1e94d82b

5. I think the client only has one (1) private content, but it doesn't seem to be causing the error as this was included in the export.

After changing the reportstatuscode as said in item # 3, and excluding some other contents with warnings in the export list, I was able to successfully get the export content. We'll try importing this and see if it works.

Thanks,

Jasper Dan Estareja

Business Intelligence Specialist

l96

+63 926 039 0740

C3C6C1

 

The information contained in this communication is confidential and is intended only for the use of the addressee. It is the property of Mitratech Holdings, Inc. Any unauthorized use, disclosure or copying of this communication or any part thereof is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately and destroy this communication and all copies thereof, including all attachments.

On Fri, 20 May 2022 at 12:18, Yellowfin Support <support@yellowfin.bi> wrote:

photo
1

Hi Jasper,


Thanks for the info.

I think its looking for associate reports while exporting (drill relation) and failing because their status is deleted.

Please let me know how the import goes.


Thanks,

Deepak

photo
1

Hi Deepak,

Looks like it was really affected by those deleted reports.

We were able to proceed with the export yesterday.

You may now close this ticket.

Thanks,

Jasper Dan Estareja

Business Intelligence Specialist

l96

+63 926 039 0740

C3C6C1

 

The information contained in this communication is confidential and is intended only for the use of the addressee. It is the property of Mitratech Holdings, Inc. Any unauthorized use, disclosure or copying of this communication or any part thereof is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately and destroy this communication and all copies thereof, including all attachments.

On Tue, 24 May 2022 at 07:12, Yellowfin Support <support@yellowfin.bi> wrote:

photo
1

Hi Jasper,


Thanks for the update. I am glad that we were able to find a way through.

I will go ahead and mark this as resolved.


Thanks,

Deepak