RE:
It seems like this would be a built in feature, but it's excluded. Why have a title for a slicer when the header works just fine? And why doesn't the slicer header automatically text wrap, but a title for a slicer does?Microsoft, stop giving us half-baked software!
RE:
We are encountering more and more scenarios that could be solved by being able to capture a picture on the mobile device and attach to a record in D365 F&O.
RE:
100% agree, thank you Sofia!
RE:
I don't know how to attach a screenshot for this bug.
RE:
The inability to expose report attributes for consumption into a metadata repository is quite a detractor for use of the tool. This metadata is not only integral for understanding what is in a report but also necessary for data privacy and security efforts. In today's world this is a must have. Looking forward to hearing about a solution.
RE:
Please let us know when can we expect this to be resolved by.
RE:
I believe the challenge is Microsoft needs a way to expose the metadata at a report attribute granularity. If they could expose this metadata, I am pretty confident Collibra could ingest it. Is this on Microsoft's timeline?
RE:
It's not a nice-to-have but a must-have for organizations that want to show proper report catalog with lineage. Is there any update on this?
RE:
This is definitely needed. There is indeed a Collibra connector but it does not work because there is no way of showing the data lineage of what data elements are being used in a report and the metadata behind it.