Closed ianneub closed 2 months ago
Is there any reason why this is not being accepted? Seems like a reasonable and easy fix.
Hey @gnongsie - can we get this PR merged into master? Seems to be a good fix for #180
We are relying on the API specification / XSD as the source of truth, and not the documentation, which may be a bit delayed in updating the details. In any case, the docs are also in agreement that this field should be a numericString. I am closing this PR as I do not see it as valid anymore.
Actually, correction. I must apologize here. This change is valid and I will include it in my own pull request.
customerProfileId
should not be aNumericStringsType
, it is a simple string.This will fix the issue in #180 .