Windows-itpro-docs: Export-StartLayout -UseDesktopApplicationID

[tylerswire]

For <-UseDesktopApplicationID> can it be explained what the change is for & does it pertain to >1809? If so, the page content might should be updated.

https://docs.microsoft.com/en-us/windows/configuration/customize-and-export-start-layout#export-the-start-layout

[mypil]

@tylerswire - Thank you for submitting feedback.

I will get this issue over to the Win10 ITPro writing team for investigation.

Thank you for reporting and making the docs better. Much appreciated.

I made a note to request the team to update this when the work is complete.

[get-itips]

Hello @tylerswire

Thanks for your feedback.
You can get full details of that parameter in the documentation for the cmdlet, here and you can see the pr that added this information.

I will create a pull request proposing to specify that it applies to versions >= 1809 to the article you referenced.

Thank you

[mypil]

@tylerswire - From our understanding, the issue has been resolved based on the merged commit https://github.com/MicrosoftDocs/windows-itpro-docs/commit/08776acb733b6b1465dab008a6f21306ae084dad but it may take a few days for the merged content to appear in the article. If you feel it hasn't been resolved, please re-open this issue.

Thank you for your contribution to make the docs better! Much appreciated!

[tylerswire]

@mypil @get-itips - Thank you for looking into this. I do not see the updated content. How long should the merge promotion take?

[illfated]

Looks like the migration process has not included the commit from 12 days ago (commit https://github.com/MicrosoftDocs/windows-itpro-docs/commit/08776acb733b6b1465dab008a6f21306ae084dad).
Maybe someone could check why that commit has not migrated yet?

[get-itips]

Looks like the migration process has not included the commit from 12 days ago (commit 08776ac).
Maybe someone could check why that commit has not migrated yet?

@kenwith Can you?

[kenwith]

Yes, will ask right now.

[kenwith]

Evidently there was a merge conflict with another repo that syncs with this repo.. someone is resolving it now and then this PR should go live.

[get-itips]

Evidently there was a merge conflict with another repo that syncs with this repo.. someone is resolving it now and then this PR should go live.

Thank you

[tylerswire]

I'm seeing the update now. Thx all!