Search
My Products
Help
erik-kle
PARTNER
PARTNER

Filter customer on attribute, 500 Internal server error

‎02-09-2020 15:02
by erik-kle (Updated ‎02-02-2021 13:41 by Yıldırım VISMA )

When trying to filter customer on attribute, i get response 500. Is this a known bug or im i doing something wrong?

 

https://integration.visma.net/API/controller/api/v1/customer?attributes={"EXID":"97089"}&pageNumber=...

 

Response

<body>
    <h1>HTTP Status 500 - Internal Server Error</h1>
    <hr />
    <p><b>type</b> Exception report</p>
    <p><b>message</b>Internal Server Error</p>
    <p><b>description</b>The server encountered an internal error that prevented it from fulfilling this request.</p>
    <hr />
</body>
Categories:
0 Kudos
10 REPLIES 10
Magnus Johnsen
VISMA
VISMA

‎02-09-2020 15:32
by Magnus Johnsen

Hi,

 

We have been able to reproduce this and will open a case with the development team.

We'll get back to you as soon as we have more information.

0 Kudos
Magnus Johnsen
VISMA
VISMA

In response to Magnus Johnsen
‎03-09-2020 07:43
by Magnus Johnsen

Hi,

 

We have checked this, and with encoding it works as expected.

E.g:

Customer?attributes=%7B"Test":"TestValue"%7D

 

Have you recently implemented this, or do you have a date of when it was working for you previously?

 

Thank you. 

0 Kudos
erik-kle
PARTNER
PARTNER

In response to Magnus Johnsen
‎03-09-2020 07:58
by erik-kle

I have used this for a long time, but havent noticed when it stopped working. Im developing a new integration now and during debugging i found it no longer works. 

 

Ill try with endcoding. 

0 Kudos
Magnus Johnsen
VISMA
VISMA

In response to erik-kle
‎03-09-2020 08:03
by Magnus Johnsen

Ok, thank you. 

Have you noticed that previous integrations have stopped working? Or is it as of now, only recent testing?

In your previous integrations, do you encode all special characters?

0 Kudos
erik-kle
PARTNER
PARTNER

In response to Magnus Johnsen
‎03-09-2020 09:36
by erik-kle

I have not used encoding for this previously, so other integrations most likely fails because of this. But I use this to find a customer based on an external id, so if this request fails, i create a new customer instead. So everything works, but maybe not in the intended way. No client have yelled at me, yet anyways 🙂

0 Kudos
Magnus Johnsen
VISMA
VISMA

In response to erik-kle
‎03-09-2020 10:45
by Magnus Johnsen

Hi,

 

We have checked the logs extensively and it looks like all of your requests when searching for the attribute parameter has been been going through.

 

How many times did you experience this result?

From where did you make this request?

 

In our test we tried this in postman, and we have learned that postman no longer autoencode, which causes this issue as the brackets are now getting rejected by the server. 

0 Kudos
erik-kle
PARTNER
PARTNER

In response to Magnus Johnsen
‎16-09-2020 08:51
by erik-kle

Hi again, returning to this thread when i think i have found the real issue.

 

My url is escaped fine and works: customer?attributes=%7B%22TESTID%22:%221518%22%7D

 

But when applying pagination it no longer works

 

customer?pageNumber=1&pageSize=10&attributes=%7B%22TESTID%22:%221518%22%7D

0 Kudos
Magnus Johnsen
VISMA
VISMA

In response to erik-kle
‎16-09-2020 09:15
by Magnus Johnsen

Hi,

 

We have tried this out and can't see any issues:

customer?pageNumber=1&pageSize=100&attributes=%7B%22test%22%3A%22testvalue%22%7D

 

What error are you getting now?

0 Kudos
erik-kle
PARTNER
PARTNER

In response to Magnus Johnsen
‎16-09-2020 10:21
by erik-kle

i get 200 but empty response body

 

[]

 

 

 

 

0 Kudos
Trygve Storrønningen1
PARTNER
PARTNER

In response to erik-kle
‎16-09-2020 10:24
by Trygve Storrønningen1

This is then problem with filtering and pagination -- also described here:

https://community.visma.com/t5/Forum-in-Developers-Visma-net/Issue-with-filtering-of-attributes/m-p/...

 

Choose your region:
Choose your Region
Go