we don't do anything special for BIP report extractions, they run the exact same way. all the hash values are done on the local database side, not the cloud. we literally have all of the metadata for a report or a pvo in a table and simply generate tables and stored procedures to handle the mergers (along with some index…

I don't know about a use case, its just how we handle importing the extracted PVO datasets into our local copy. to elaborate: Let's pick a relatively simply pvo FscmTopModelAM.FinExtractAM.GlBiccExtractAM.BalanceExtractPVO we import that data every 2 hours by grabbing the csv/pecsv files off the ucm. For each csv file, we…

What we do is the following: Import the extract to a staging table and calculate a hash (sha-256) there. That hash along with the primary keys (things change if the keys can be null of course) are used in a T-Sql merge statement in our primary warehouse, so we are only updating/touching rows that actually have a changed…

Got mine yesterday.

Its posted on the first message of this thread. make sure you look on page 1

I got a notice that the voting on this idea is open, considering it was open, I'm not sure what that means, but I'm hopeful once more.

I don't think 24D information is available yet.

I haven't seen or heard anything on this idea.

@Bret Grinslade - Oracle Analytics-Oracle I would take this in any format I can get it. To me, it would be a highly useful feature. Do I now need to take this idea submitted nearly a year ago and put it into a new area to have it even looked at?

Hi there, to be 100% honest with you, I don't really remember. In general, we have pivoted over to regenerating the reports out of PVO's where this is an issue, however, one trick to try is on the data model, make sure the Include Parameter Tags option is enabled. That should force the headers to generate.