Failed Data Reporting - Alias Names across Environments
We have Info Steward on 3 environments : Dev, Integ, Prod.
There are also have 3 Failed Data Repositories, 1 for each of the above.
Now we want to do some custom reporting against the FDR.
Normal process would dictate to develop these views on the Dev FDR, then migrate to Integ and through to Prod.
However, what I am seeing is this.
I have table ECC.MARA in my IS project, and on Dev, the failed data gets dumped into FDR with alias "MARA_123"
But if I now look in the same project on Iteg, the alias for the same data tables is 'MARA_345'.
Again, looking in prod, the alias if different again 'MARA_567'.
Obviously this make it impossible to create a view against the alias in Dev, and simply migrate it through to the other environments.
Yes, of course I can work around this, but the effort, in my opinion, is way way above what should otherwise be a simple process.
(I'm currently looking at scripts that accept FQ table attributes and then look up alias to dynamically build views/procedures from template)
So now I am curious ... do other people see this same phenomenon ?
Is there a mechanism to 'fix' aliases across environments ?
How do you work with it/around it/fix it ?
Appreciate any enlightenment on strategies for custom reporting in this context !