Skip to content
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

TimeEntries 404 Error #60

Open
blabelle-sB opened this issue Mar 19, 2024 · 2 comments
Open

TimeEntries 404 Error #60

blabelle-sB opened this issue Mar 19, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@blabelle-sB
Copy link

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.

@blabelle-sB blabelle-sB added the bug Something isn't working label Mar 19, 2024
@blabelle-sB
Copy link
Author

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?

@TheMonzel
Copy link
Contributor

Did you run Get-AutotaskAPIResource before New-AutotaskAPIResource? If so, I guess this is related to #49

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants