Closed FabianCretton closed 1 year ago
This message should be displayed
@tpluscode do you mean that this is working, or that this should be done ? Yesterday Tobias contacted me because of a mapping problem, and it was because he did not run the transform again, so I guess he never saw the message
Yes, this message is already shown after mapping. So unless there are specific circumstances in which it does not, I might assume that Tobias simply missed it
@tpluscode is the message always present when you re-open the cube, or only just after doing the mapping ?
This message is persistent, displayed in the Cube Designer screen
So, I did not see the message this morning when opening his cube
See his cube: https://int.cube-creator.lindas.admin.ch/app/cube-projects/cube-project!!swissprtronlytrucatedpq2-g21lpjwoq9/metadata Dimension 'Betriebs ID' I will ask him to wait before transforming
Another curiosity, if you look at this:
Very strangely, on that cube, if you open the mapping -> each value has 2 entries, for instance "101", one being mapped, the other one not:
That is quite curious. Maybe related to #1314. I will look into that
Another curiosity, if you look at this:
I found this behaviour being caused by data type of Betriebs ID
. The mapping itself is string => shared term
but the IDs are numbers. (The identifiers of that particular dimension are string too, but that may be irrelevant)
Bottom line, I think the mapping should operate on the raw string value of a mapped dimension. @l00mi
Sorry @tpluscode that we mixed two things in this talk. I think you talk here about why we see twice each value, right ?
But what about the 'transform' message that do not show up, did you find anything or is it a mistake on my side ?
Yes, I can also confirm that the message did not appear as it should have. Will handle that next.
I focus on the mapping itself because the string vs number mismatch actually breaks the mapping functionality. I mean, yes it would be possible to work around by mapping from CSV to string
but I think it's an unnecessary restriction
Thanks, I thus wait for your update
I did find two circumstances when the warning was not displayed: when auto-filling the mapping and when mapped pairs were removed only, without adding any new. Both being fixed now
@tpluscode I only just saw this thread. Maybe to give a bit of clarification from my part: It indeed was done via auto-filling the mapping from a shared dimension i created earlier. However when doing the transformation even without the displayed warning message the SD for some reason did not link properly (or at all for that matter). This is the Cube in question
Than you for the clarification @tboeni. I believe both your problems will be fixed with next release
On step 3, when we map a dimension to a Shared Dimension, we then need to go back to Step 2 and transform again, right ? And we talked about having a user message to inform him when a new transformation is needed, but if I am not mistaken, there is no information displayed after a new Shared Dimension mapping.
Thank you for any input