Use include query param to include more than 3 custom fields in entity responses #31
Conversation
This file contains hidden or 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
Contributor
|
Thanks for your PR. |
Author
|
https://developer.intuit.com/app/developer/qbo/docs/workflows/create-custom-fields/get-started Towards the bottom of this page is where I saw it mentioned. I've been unable to find it being documented anywhere, but it does work for my realm at least. Maybe it could be a good idea to make the addition of this param optional? |
Author
|
@clement911 Howdy, just checking in to see if you have any thoughts on this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adding "include=enhancedAllCustomFields" to the URL query parameters for requests that return Entities will allow the API to return more than 3 custom fields.