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

}bedrock.cube.data.import fails if _}CubeProperties does not exist #418

Open
onefloid opened this issue Nov 18, 2024 · 0 comments · May be fixed by #419
Open

}bedrock.cube.data.import fails if _}CubeProperties does not exist #418

onefloid opened this issue Nov 18, 2024 · 0 comments · May be fixed by #419
Labels

Comments

@onefloid
Copy link
Contributor

Describe the bug
I have found another (nice) edge case. If the }CubeProperties cube does not exist, }bedrock.cube.data.import fails for parameters pLogging 0 and 1. The error message is:

Prolog procedure line (992): Cube "}CubeProperties" Not Found

To Reproduce
Steps to reproduce the behavior:

  1. Set up a new plain TM1 V11 Instance. Doublecheck that the }CubeProperties is not present.
  2. Run with parameters pLogging = 0
  3. The result is the error message from the description

Expected behavior
The }CubeProperties should be created implicitly.

Solution
Instead of reading the value directly from the cube, retrieve the logging status using CubeGetLogChanges(). This function creates the }CubeProperties if needed.

Version

  • OS: Windows Server 2016
  • TM1 Server Version: 11.8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant