Update TripPin.pq #259
Merged
Update TripPin.pq #259
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By default, the `Table.FromRecords` function utilizes the column names from the first record for the remaining records. If that record is missing columns, the rest of the records will be NULL. More problematic, however, is when responses from multiple pages of an API request have different sets of fields. In this case, the paged function doesn't know how to stitch the individual pages back together because they have different column counts. This is not uncommon from APIs that remove NULL values from the response. Passing the schema columns names into this `Table.FromRecords` function does prevent the overall flow from being "dynamic", but it prevents errors when responses within a paged route are different. The `SchemaTransformTable` function can still be used, it's main value being to set column types.
mattmasson
approved these changes
Nov 19, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, the
Table.FromRecordsfunction utilizes the column names from the first record for the remaining records. If that record is missing columns, the rest of the records will be NULL. More problematic, however, is when responses from multiple pages of an API request have different sets of fields. In this case, the paged function doesn't know how to stitch the individual pages back together because they have different column counts. This is not uncommon from APIs that remove NULL values from the response.Passing the schema columns names into this
Table.FromRecordsfunction does prevent the overall flow from being "dynamic", but it prevents errors when responses within a paged route are different. TheSchemaTransformTablefunction can still be used, it's main value being to set column types.