on 04-03-2018 3:59 PM
We are on BI 42 SP5 P100, Configured Live data connectivity for SAC. I was able to successfully create connection from SAC tenant URL to our BI server.
However, When I try to create a model from a simple universe I get this error: app.chunk.modeller-chunk.e4dd699aa3ab086039f8.js:29 Uncaught (in promise) TypeError: Cannot read property 'metadata' of undefined"
Has anyone run into this issue?
Hi Ole,
What we noticed is that the unx needs to be customized for analytics cloud. I created a simple universe with 8 dimension objects and measure and that seems to work but not our existing universes. Seems like there are many restrictions:
Please check this link I found: https://wiki.scn.sap.com/wiki/display/BOC/SAP+Analytics+Cloud+Support+Matrix#SAPAnalyticsCloudSuppor...
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi rpuranik Hi ole.bisgaard
yes that's right, BI's e-fashion sample universe has "multiple contexts" in its design, which currently can't be handled by SAC's live universe connector (the 'import data' connector can cope..). This is a planned enhancement before long.
If customers are looking for a way of adapting their existing (complex?) BI universes, so that SAC's live connector works, then i recommend using this wiki/guide here: https://wiki.scn.sap.com/wiki/display/BOC/SAP+Analytics+Cloud+-+Live+Universe+Design+Best+Practices
OK, so a few 'tweaks' need to be made so that the UNX is readable by SAC, but creating a derived universe to 'simplify the outline' is not the end of the world, actually it kinda helps with self-service.
However, one needs to remain vigilant here: Quite a few fundamental features are currently not in scope at all (referring back to Roopa's link, the support matrix. ) This includes stuff like: Projection function 'count'; Data types: Date & DateTime; Detail Objects; Complex List of Values etc.
So this might be tricky for existing BI customers who'll potentially need to significantly remodel some aspects of their universe-investment; but, hopefully for customers who are developing new, lean universes for emerging use-cases, then they should be able to take these boundary limitations into account from the outset of the development exercise.
Kind regards,
H
Hi Roopa,
Yes, I have seen this error and I reported it to development:
https://launchpad.support.sap.com/#/notes/2635444
They are currently testing the fix in newer waves of the product. You can identify in Tomcat logs why the Universe cannot be used.
The error should be passed to the user indicating something like: the universe contains contexts that currently are not supported. Instead, you get this behaviour. But ultimately, what it indicates is that this universe can't be used.
Regards,
Julian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.