Skip to content

Error "ForceGet" paramametter in method "getModelviewProperties" #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Feb 4, 2019

Conversation

edneyego
Copy link
Contributor

We encountered a problem in the forge API for Java Ver. 1.0.1.

When submitting the DWFx file to the modelDerivative API and trying to get its properties the system returns the following error -> {"diagnostic": "Please use the 'forceget' parameter to force querying the data."} that 20mb)

However, the fix refers to a parameter of type QuereParam to be submitted to the API.
Ex: derivativesApi.getModelviewProperties (base64Urn, guid, "{" forceget \ ": true}", oauth2TwoLegged, twoLeggedCredentials);

But the Forge API for Java in version 1.0.1, in the "getModelviewProperties" method, line 376, the List Pair of queryString is instantiated. but in the "getAPIResponse" method, in ApiClient it builds the "forceget" in the URL not as a queryParam but as an ACCEPT Enconding. (as shown in the image).

@xiaodongliang xiaodongliang merged commit ce3fadd into Autodesk-Forge:master Feb 4, 2019
@xiaodongliang
Copy link
Collaborator

xiaodongliang commented Feb 4, 2019

Hi @edneyego ,

thank you much finding this! sorry we did not have chance to merge until today.

When checking the update, it is not clear to me with JacksonMapper you created to append query string array to localVarQueryParams because it looks we can simply add an pair array to an empty array directly. In addition, although there is only one query string with GET:Metadata and GET:Properties, it might happen more parameters would be added in the future. So it will be more extensible to define it as an array.

I will commit my update based on yours. Please feel free to PR if anything you would suggest to update.

-Xiaodong

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants