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
Running the command "$Body = New-AutotaskBody -Resource TimeEntries" gives the error "New-AutotaskBody : Getting object failed: The remote server returned an error: (404) Not Found."
Creating the body in powershell directly and then running "New-AutotaskAPIResource -Resource TimeEntries -Body $Body" fails with the same error.
I have reproduced this on 2 devices, while it works on another 2. One of the ones that's not working is Azure Automate and I've tried powershell 5.1 as well as 7.2 with the same results in Azure. I've tried forcefully uninstalling and re-installing the module on my local computer.
The text was updated successfully, but these errors were encountered:
I've found that using the "Add-AutotaskBaseURI" command fixes the issue. For some reason the other commands work without having to specify the uri, but the timeentries flag does not work if I don't specify the uri. What's more strange is that I need to run the "Add-AutotaskBaseURI" command immediately before the New-AutotaskAPIResource command. If I run it at the beginning of my script, it doesn't stick. Is there a way to make that stick so I don't have to re-run it before every command?
Running the command "$Body = New-AutotaskBody -Resource TimeEntries" gives the error "New-AutotaskBody : Getting object failed: The remote server returned an error: (404) Not Found."
Creating the body in powershell directly and then running "New-AutotaskAPIResource -Resource TimeEntries -Body $Body" fails with the same error.
I have reproduced this on 2 devices, while it works on another 2. One of the ones that's not working is Azure Automate and I've tried powershell 5.1 as well as 7.2 with the same results in Azure. I've tried forcefully uninstalling and re-installing the module on my local computer.
The text was updated successfully, but these errors were encountered: