API Error

smcs

Updated instance this morning, went to create a new client which all works but when I went to add assets in TRMM, they failed. I investigated the issue and discovered that now when I create a new client it gives the Client ID and Location ID the same number so the api call fails. Was this by design or?

Is anyone else having the same issue with same Client and Location ID?

I did check the same on demo site and it doesnt do it. Can someone help me resolve this?

Update - If I archive the first location and create a new one it increments the number by 1 so it is a workaround butI would like to know what is happening, never had issues until today.

wrongecho

smcs

You mean to say you have two clients in ITFlow with the same ID? That should be impossible as the client_id database column is unique & auto increment..

smcs

No, I created a client and got an id, i created a location for that client and it gave it the same id number, so now the api call fails because the client id and location id are the same. If I archive the first location and create another one it increments the number by 1 then it all works again. I havent changed anything at all, so I am not sure what happened. I havent had to create any clients for awhile so not sure exactly when this started.

wrongecho

It seems like this just happened to be client id 69 and location id 69. I don't know why that would affect anything on the API?

smcs

Hmmm something very odd, not sure whats up. With this client I cant even archive the location. I am going to delete the client and recreate. maybe it was an issue when it was first created. I will report back.

smcs

Recreated all and did get new id and different location id but its still failing for this client. I am not sure whats happening because it works for all of my other clients that I already had in the portal. I will just have to wait for another new client and see what happens. Appreciate your feedback as always!

wrongecho

Really odd. Worth checking the audit logs and php logs

smcs

Thank you for that info, I checked and I can see the issue is from the computers at that location, it seems they cant get to the api which is weird because i can get to it by web browser so there is something on that network blocking the communication. Mystery solved thanks to your help! Really appreciate you @wrongecho

wrongecho

smcs

I think the matching client id and location id just made it seem weird haha.

You're welcome - Glad you figured it out 🙂