Table.TransformColumnTypes - Identifying which transformation functions are used#300
Conversation
|
@bgribaudo : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 8518a0e: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
|
||
| The type value in the `typeTransformations` parameter can be `any`, all of the `number` types, `text`, all of the `date`, `time`, `datetime`, `datetimezone`, and `duration` types, `logical`, or `binary`. The `list`, `record`, `table`, or `function` types aren't valid for this parameter. | ||
|
|
||
| For each column in `typeTransformations`, the ".From" method corresponding to the specified type value is used to perform the transformation. For example, if a type value of `Currency.Type` is given for a column, the transformation function `Currency.From` will be applied to each value in that column. |
There was a problem hiding this comment.
Consider adding "normally" below, because there are a few, ultra-obscure edge cases where that's not the case, but I don't think it's worth enumerating them.
| For each column in `typeTransformations`, the ".From" method corresponding to the specified type value is used to perform the transformation. For example, if a type value of `Currency.Type` is given for a column, the transformation function `Currency.From` will be applied to each value in that column. | |
| For each column in `typeTransformations`, the ".From" method corresponding to the specified type value is normally used to perform the transformation. For example, if a type value of `Currency.Type` is given for a column, the transformation function `Currency.From` will be applied to each value in that column. |
There was a problem hiding this comment.
Thanks, @ehrenMSFT! How does it look now?
|
@bgribaudo : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 620b162: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
@ehrenMSFT, you have me curious. Even though documenting them doesn't belong on this page, any chance you'd be willing to share the edge cases where the corresponding |
I don't know much about the scenario, but there are cases where the presence of certain metadata on the column type indicates that a number value comes from the Windows filesystem. In that case, we call DateTime/DateTimeZone.FromFileTime instead of From. There are also cases where, based on a flag, we can convert to list or record using an "as" operation. But this seems to only be used internally in the JSON library. |
|
Learn Build status updates of commit d1fe95c: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
@DougKlopfenstein - Could you review this proposed update to your article and enter |
|
#sign-off |
Thanks, @ehrenMSFT! |
No description provided.