Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update }bedrock.cube.data.export.pro #428

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

wimgielis
Copy link
Contributor

Existing public views should not be recreated. The use case is that views already exist (typically with filters applied) and then a simple call to '}bedrock.cube.data.export' with the name of the view and pFilter = '' would reset the view and remove the filters. That reset is done in '}bedrock.cube.view.create' but probably best to not break into that process.

Existing public views should not be recreated. The use case is that views already exist (typically with filters applied) and then a simple call to '}bedrock.cube.data.export' with the name of the view and pFilter = '' would reset the view and remove the filters. That reset is done in '}bedrock.cube.view.create' but probably best to not break into that process.
@wimgielis
Copy link
Contributor Author

My main use case why I would suggest this behaviour is the following.

With }bedrock.cube.data.export we can export with filters. However, pFilter does not support MDX subsets. Hence, exporting becomes difficult with }bedrock.cube.data.export as we can only have let's say hardcoded elements or short lists of elements.

When we add the possibility to export with filters, the only solution I see is a 3-step approach:

  1. create view with Bedrock
  2. assign subsets to the view, subsetse that are the result of MDX queries
  3. export the view data with Bedrock BUT pFilter = '' because we cannot override the filters and we supply the view name.

Hence in step 3 Bedrock should not recreate or reset the existing view or it would throw away the work done in step 1 and 2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant