Power Query: Changing exception -> error#385
Power Query: Changing exception -> error#385v-regandowner merged 4 commits intoMicrosoftDocs:mainfrom
Conversation
prmerger-automator
bot
requested review from
DougKlopfenstein,
ehrenMSFT and
whhender
|
@bgribaudo : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
bot
added
Change sent to author
m-source/subsvc
powerquery/svc
labels
|
Learn Build status updates of commit 1843241: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
There was a problem hiding this comment.
Pull request overview
This PR updates Power Query documentation to use the correct M language terminology by replacing "exception" with "error" across multiple function documentation files. The M language/Power Query does not have a concept of exceptions but instead uses errors.
Changes:
- Updated 16 documentation files to replace "exception is thrown" with "error is raised"
- Changed "function throws an exception" to "function raises an error"
- Aligned terminology with existing Power Query/M language documentation standards
Reviewed changes
Copilot reviewed 16 out of 16 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| table-transformcolumns.md | Changed "exception is thrown" to "error is raised" in column operation documentation |
| table-reordercolumns.md | Changed "exception is thrown" to "error is raised" in column reordering documentation |
| table-renamecolumns.md | Changed "exception is thrown" to "error is raised" in column rename documentation |
| record-removefields.md | Changed "exception is thrown" to "error is raised" in field removal documentation |
| record-fromtable.md | Changed "exception is thrown" to "error is raised" in record creation documentation |
| record-field.md | Changed "exception is thrown" to "error is raised" in field access documentation |
| logical-totext.md | Changed "exception is thrown" to "error is raised" in logical value conversion documentation |
| logical-fromtext.md | Changed "exception is thrown" to "error is raised" in text to logical conversion documentation |
| list-standarddeviation.md | Changed "exception is thrown" to "error is raised" in standard deviation documentation |
| list-single.md | Changed "throws an exception" to "raises an error" in single item retrieval documentation |
| list-modes.md | Changed "exception is thrown" to "error is raised" in modes calculation documentation |
| list-mode.md | Changed "exception is thrown" to "error is raised" in mode calculation documentation |
| list-lastn.md | Changed "exception is thrown" to "error is raised" in last N items documentation |
| list-functions.md | Changed "throws an exception" to "raises an error" in List.Single summary |
| datetimezone-switchzone.md | Changed "exception is thrown" to "error is raised" in timezone switching documentation |
| custom-date-and-time-format-strings.md | Changed "exception is thrown" to "error is raised" in format string documentation |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ### Using single custom format specifiers | ||
|
|
||
| A custom date and time format string consists of two or more characters. Date and time formatting methods interpret any single-character string as a standard date and time format string. If they don't recognize the character as a valid format specifier, they throw an expression error. For example, a format string that consists only of the specifier "h" is interpreted as a standard date and time format string. However, in this particular case, an exception is thrown because there is no "h" standard date and time format specifier. | ||
| A custom date and time format string consists of two or more characters. Date and time formatting methods interpret any single-character string as a standard date and time format string. If they don't recognize the character as a valid format specifier, they throw an expression error. For example, a format string that consists only of the specifier "h" is interpreted as a standard date and time format string. However, in this particular case, an error is raised because there is no "h" standard date and time format specifier. |
There was a problem hiding this comment.
The same sentence contains both "they throw an expression error" and "an error is raised", creating inconsistent terminology. For consistency with the rest of the documentation and the purpose of this PR, "they throw an expression error" should also be changed to "they raise an expression error" or "an expression error is raised".
There was a problem hiding this comment.
This AI feedback is actually correct. Ben, can you make this change?
There was a problem hiding this comment.
Thanks, @ehrenMSFT. Updated and simplified.
| ### Using single custom format specifiers | ||
|
|
||
| A custom date and time format string consists of two or more characters. Date and time formatting methods interpret any single-character string as a standard date and time format string. If they don't recognize the character as a valid format specifier, they throw an expression error. For example, a format string that consists only of the specifier "h" is interpreted as a standard date and time format string. However, in this particular case, an exception is thrown because there is no "h" standard date and time format specifier. | ||
| A custom date and time format string consists of two or more characters. Date and time formatting methods interpret any single-character string as a standard date and time format string. If they don't recognize the character as a valid format specifier, they throw an expression error. For example, a format string that consists only of the specifier "h" is interpreted as a standard date and time format string. However, in this particular case, an error is raised because there is no "h" standard date and time format specifier. |
There was a problem hiding this comment.
This AI feedback is actually correct. Ben, can you make this change?
|
@bgribaudo - Before you can merge this pull request, you need to update from main to remove the branch conflicts. Resolving one of the conflicts in table-transformcolumns.md will delete your change, so you'll need to add your change back into the file. |
|
Learn Build status updates of commit 75c2158: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
|
Learn Build status updates of commit 21639ab: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
Thanks, @DougKlopfenstein. |
|
Learn Build status updates of commit e2d040b: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
@DougKlopfenstein - Would you add a comment to indicate what action to take on this PR? Thanks! |
|
Thanks, @ehrenMSFT! |
|
#sign-off |
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @whhender |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 15 out of 15 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
7 participants
In various places, Power Query documentation refers to exceptions being thrown. However, the M language/Power Query does not have a concept named "exceptions." Instead, I believe the correct Power Query/M terminology is actually errors being raised.
Updating docs to reflect.