Issue with creating a ticket attachment

[musa-isofer]

Hi, here's the command and errors I am receiving when trying to create a ticket uri attachment:

PS New-AtwsAttachment -Title 'test attachment' -URI 'https://testattachmenturl.com/examplesite' -TicketID $ParentTicketObject.id -Publish 'Internal Users Only' -Debug -verbose
DEBUG: New-AtwsAttachment: Begin of function
DEBUG: Get-AtwsPicklistValue: Begin of function
VERBOSE: Get-AtwsPicklistValue: Looking up detailed Fieldinfo for entity AttachmentInfo
VERBOSE: Get-AtwsPicklistValue: Entity AttachmentInfo has picklists and field ParentType has 17 picklist values.
DEBUG: Get-AtwsPicklistValue: End of function
VERBOSE: New-AtwsAttachment: About to create an attachment of type URL with title test attachment.
MethodInvocationException: C:\Users\<UserProfile>\Documents\PowerShell\Modules\Autotask\2.0.3\Public\New-AtwsAttachment.ps1:399
Line |
 399 |              $AttachmentId = $Script:Atws.CreateAttachment($Script:Atw …
     |              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Exception calling "CreateAttachment" with "2" argument(s): "System.Web.Services.Protocols.SoapException: Missing
     | Required Field: ParentType.     at autotask.web.services.API.v1_6.ATWS.CreateAttachment(Attachment attachment)
     | at AutotaskApiApplication.API.V1_6.AutotaskApiService_1_6.CreateAttachment(Attachment attachment)"
Get-AtwsAttachmentInfo: C:\Users\<UserProfile>\Documents\PowerShell\Modules\Autotask\2.0.3\Public\New-AtwsAttachment.ps1:401
Line |
 401 |              $result = Get-AtwsAttachmentInfo -id $AttachmentId
     |                                                   ~~~~~~~~~~~~~
     | Cannot validate argument on parameter 'id'. The argument is null or empty. Provide an argument that is not null
     | or empty, and then try the command again.
VERBOSE: New-AtwsAttachment: Created attachment with id  and title
DEBUG: New-AtwsAttachment: End of function

[musa-isofer]

Update on this, I was able to do this with the rest api outside the module. As such, can you create a function called "Invoke-AtwsRequest" so that users can call custom api requests? Similar to invoke-mggraphrequest from the Graph API powershell module. That way if there are issues with some functions or if we need to construct our rest call in a specific way, we won't have to work outside the module.