Skip to main content
To homepage To homepage

Dear Community,

When I create a view in my data area MDW from a table which is in my DSA (=> I drag the table from my DSA are to the views in the MDW data area), the view auto parameterizes (which is great). I deploy the view in the MDW, read view fields and preview it. (all is still great).

When I release this to my next layer (PRD) I suddenly get a erroer previewing the MDW view. When I check the view in the PRD MDW the parameterization is all gone.

Have you encountered this? Is there a solution?

Thanks

= Daniel

Hi,

interesting approach - I typically create a view in DSA and then map it to tables in MDW. Does it matter whether you Map Custom View fields (you always should anyway)?

I take it when you say PRD you mean another instance? Has that been deployed yet? It could be that the schema the view exists in does not exist or something similar? I would expect an error, so this seems to not entirely work properly.

Hey @rory.smith ,

It is an interesting approach and I’ve fixed it a different way. It is just that I did not expect thios behavior from TX and wanted to check.
So yes, when i say PRD I mean an other Instance. So I’ve got a table in my DSA data area and then drag this to my MDW data area views section. Drop table, create the view (with parameterization as it will do this automatic) and keep the view in this section to be queried by other process. Deploy and Execute everything.

After: I transfer the Instance from DEV to PRD, I deploy and execute everything it all seems to work fine. But when I query the view I get an error saying that it cannot find the underlying table (this is the Parameterized table from the DSA). When I Check the view all the parameterization is gone. thats why it doesnt work. But I do not expect this type of behavior.

@Christian Hauggaard : maybe I can try and recreate this issue?

Hi,

sounds like a bug - but maybe there is one more step to test: after deploying in PRD, if you read view fields, does that change anything?

I guess if you write your view unparameterized with fully qualified table it will keep working as there is no parameter → syntax transformation required. I think DSA.table → DSA.custom view → MDW.table should work (it did in the past anyhow). That might be good to check as well. Does mapping the custom view fields effect any change or do those mappings also get lost?

Hi @daniel 

I have managed to reproduce the issue. I have passed this onto the product team and will let you know once I have an update

Hi @daniel 

A fix has been released for this in 

  • Parameters would be removed from custom views created using drag-and-drop between two data areas.

@Christian Hauggaard : that's amazing! And really fast. Thanks!

Reply


Terms and ConditionsCookie settings