You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
make:defaults fails for ArticlePlainTextContent,Version,DocumentPlainTextContent,InventoryStockedItemsAdd,InventoryStockedItemsRemove,InventoryStockedItemsTransfer,Modules
#13
Hi there! I am working on adding a few updates to autotask-client-generator (including queries via POST to get around the GET url size limitation). In working with the generator, I've found that the following classes error out during make:defaults. Is this a known issue? Should they generally be excluded? Or is this a new problem?
I did add a --exclude=EXCLUDE so I could exclude these during the generation phase. So.. I guess that's one new feature right there. :)
I tried this against both the Autotask dev ww2 server and against a prod server ww5. Both with the same result.
Here is an example using ArticlePlainTextContent:
Generating classes for ActionTypes
Generating classes for AdditionalInvoiceFieldValues
Generating classes for Appointments
Generating classes for ArticleAttachments
Generating classes for ArticleConfigurationItemCategoryAssociations
Generating classes for ArticleNotes
Generating classes for ArticlePlainTextContent
There was an error creating that endpoint: Client error: `GET https://webservices5.autotask.net/ATServicesRest/v1.0/ArticlePlainTextContents/entityInformation` resulted in a `404 Not Found` response:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xml (truncated...)
The text was updated successfully, but these errors were encountered:
Hi there! I am working on adding a few updates to autotask-client-generator (including queries via POST to get around the GET url size limitation). In working with the generator, I've found that the following classes error out during make:defaults. Is this a known issue? Should they generally be excluded? Or is this a new problem?
I did add a --exclude=EXCLUDE so I could exclude these during the generation phase. So.. I guess that's one new feature right there. :)
I tried this against both the Autotask dev ww2 server and against a prod server ww5. Both with the same result.
Here is an example using ArticlePlainTextContent:
The text was updated successfully, but these errors were encountered: