on
RE:
This thread is marked as completed so maybe it is not getting picked up by anyone at MS
RE:
Voted! This has been for years and is still a mandatory requirement for all Sales / Purchase and Export/Import documents.
RE:
Multiple column support would help a lot. It would reduce clutter on the dashboard, and prevent user errors from searching in the wrong text box.
RE:
I found this repo on github (microsoft/Analysis-Services/blob/master/pbidevmode/fabricps-pbip) which might help.Looks like its still WIP though. And since the fabric API doesn't support service principals for the git update, its probably not enough to get full deployment support for your case.
RE:
I agree. Its' not usable due to our dependency on deployment pipelines, but very important for a good development experience.
RE:
It is legally allowed to register in Germany with the Austrian company adress. So we receive a German Tax exempt number. But in D365 we are not able to create an entry with the combination Austrian address + German Tax exempt number. A warning does not help us.
RE:
This crazy simple feature request has been under review over 2 years. Can we just approve this and add it? There needs to be a much greater range of scheduling data set and data flows. Daily and Weekly is not acceptable, also only at top and bottom of each hour is also too limiting. Why was this implemented with so many restrictions
RE:
Here we are in 2025. This important feature is not yet available in PBIRS. It would be great if we users could know when and if the export w/ the current layout will be added this year.
RE:
I agree.This would save me a lot of messing around trying to get data through custom connectors into a dataflow.Any updates on this in the roadmap?
RE:
We need this feature ASAP. I have created a duplicate ticket )i didn't know how to search for tickets)/ Requirement - Linking KA's:A KA creator must be able to link multiple KA's together.E.g. KA1 (paint wall) is linked to KA2 (Fix hole).If a KA creator creates a new version of a KA (major or minor version), AND the original KA was linked to another KA (see requirement 1), then the link between KA1 and KA 2 must not be broken.This is important as once a new version is created, you don't want the link broken.If a CRM user searches an KA using the Knowledge Search functionality, and the CRM user opens KA1 (which is linked to KA2). The CRM user must be able to open KA2 and remain the in "search UI".Currently if you link a KA using a URL, it opens the KA entity and displays information/ fields about the entity that is not relevant to an end user.