asked on January 15, 2025
We are currently connecting to our SSAS Cube's via accelerator.
We have noticed that if the cube doesn't actually exist, accelerator just picks one from the list of cubes and connect to it.
How can we prevent that behavior? I'd like it to just fail and not connect.
⋅ January 16, 2025
Hello, Robbie!
Thank you for reaching out to us.
Kindly note that Flexmonster Accelerator doesn't have the described logic for picking another cube when the necessary one doesn't exist.
If the cube doesn't exist, Flexmonster shows the corresponding message to the user. You can check it out in the following JSFiddle: https://jsfiddle.net/flexmonster/jq9gtrn6/.
We recommend checking if Microsoft Analysis Services provides a configuration to automatically locate the next available cube when the specified one is unavailable.
Hope it helps.
Kind regards,
Solomiia
⋅ February 4, 2025
Hello, Robbie!
Hope you are doing well.
Our team is wondering if there are any updates on the case.
Do not hesitate to ask if there are any other questions we can assist you with.
Kind regards,
Solomiia
⋅ February 4, 2025
If it isn't supposed to connect then there is certainly a weird bug happening.
Our developer was feeding it a cube that doesn't exist in the wrong environment, and it was loading a cube that shouldn't have.
But i think we squared it out by checking against databases and backslashing the cube name.
⋅ February 5, 2025
Hello, Robbie!
Thank you for your feedback.
We are happy to hear that you found the solution.
Feel free to reach out to us if any other questions arise.
Kind regards,
Solomiia
