Update get-best-of-standard-dataflows - Known Limitations Wording Adjustment

[bdiggydogness]

In the known limitations, I've adjusted the detail around the 'multiple-select' data load.

Through testing multiple scenarios, I have found that:

• if you try and migrate BOTH a multi-select choice column AND a single-select choice column, the dataflow will fail (and the error makes you think it's because of the multi select field).

• If you migrate just one TYPE of choice field, dataflow runs perfectly.

I think the wording needs to be clearer to outline this issue with Dataflows.

Image showing the error message received when two different choice types are selected:

Image showing the refresh history when only Multi-select choice fields are published:

[prmerger-automator]

@bdiggydogness : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 01571b4:

✅ Validation status: passed

File	Status	Preview URL	Details
powerquery-docs/dataflows/get-best-of-standard-dataflows.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Court72]

@DougKlopfenstein

Can you review the proposed changes?

When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[JasonWHowell]

#assign:ptyx507x
#assign:jonburchel

[Luitwieler]

@msftyehong I believed we already similar feedback to this page already? I think it is clear that the change proposed makes sense, however, is this the expected behavior?

[msftyehong]

@bdiggydogness mind sharing a solution with reproduction of the issue - I'm not able to reproduce, probably miss something (and for completeness, please include the other scenario that does refresh).