County-Number problem

[Florian Haase]

Hi,

we got some problems with the customer import. The problem is that there are saved some county-numbers on the customers which not longer exists due to the county-reform in Norway (I guess)

In the UI its not a problem to update the address of such a customer. But the API returns an error that county-number XXX does not exist and the customer will not be updated. 

One question is: Why is the behaviour different in UI and API here

The other is: Why has county-numbers been deleted even if they are in use. Than the customers should have been updated too. If have not checked now if there are more than the one customer we found but probably there are.

Just now we have switch off the postnumber lookup and hope that this will solve the import-problems but I actually dont know.

Regards 

Florian

[Yıldırım]

Hi, 

there is no control on the UI if "County" which is assigned on the customer card has been deleted. System does not return error if you want to change any address field apart from County when county ID left as what value has already assigned. 

If you want to update the county field then this value should exist in the relevant module otherwise both UI and API returns error.

1)Countries/counties/postcodes (screenId=CS20400S)

2)Customer Card

[Florian Haase]

Hi

yes, that is also our experiance. The problem is that we have one or several customers which have an invalid county-number. We don't know but guess that Visma maintains this county register - the customer at least did not know about it at all. 

The UI does not cause any error when updating the address fields even if the county number is invalid. (just when you try to register a wrong number in the field than it failes). But the API returns an error and does not update the customer-information even if we don't deliver any county-information in the json.

Here we have a different behavior on the API and UI.

For now we have deactivated the postnumber - lookup and hope that solves the problem on the API site but we have not really testet that - its just suggestion.

Regards

Florian

[Yıldırım]

Hello, 
County fields are auto-populated in the initial company setup then user may edit based on requirements. Unfortunately this is out of our knowledge if there are any mass updates applied by ERP.

---

@Florian Haase wrote: 

The UI does not cause any error when updating the address fields even if the county number is invalid. (just when you try to register a wrong number in the field than it failes). But the API returns an error and does not update the customer-information even if we don't deliver any county-information in the json.

---

Once customer card has been tried to be updated with non-existent County ID, it'll start to fail on both platforms. In this case we'd recommend you to remove the county value on the customer card and continue with desired operations. Afterward, user can configure the field with the valid ID. 

[Florian Haase]

This customer I got updated without any message in the UI but it will fail in the API:

[Yıldırım · Accepted solution]

We'll convey this case to the ERP. This should also return an error on the UI since that County ID does not exist and not synched correctly when the source has been modified.

Before running the API operation, please remove the assigned "county" which no longer exists and save with valid ID in the ERP UI. Then the user can also update the value with the desired one.