You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently found out by accident, that the standard EFT service implementation limits the length of (secure) string type parameter properties to 200 characters.
We're using connection strings and have implemented logging into Azure Application Insights and use the appi connection string as a payment processor parameter property.
Microsoft recently changed the contents of the Application Insights connection string to include the Application Id in it.
Previously the connection string was formatted in a way which didn’t exceed the maximum string length of 200 characters.
When you use the new type of connection string as a payment processor parameter property, it's truncated by D365FO in a way that breaks the connection string usage since the contents is missing the better part of the ApplicationId. Entering the value seemingly works just fine, you can paste the connection string value to the property field.
But after saving the changes, like said, the system truncates the string value to a maximum of 200 characters. When you pull the connection string property for use, it shows the first 200 characters of the actual connection string. The last part of the connection string is broken since it was truncated and does not contain the last delimiter and a value part.
Using the truncated connection string results in an error situation and prevents using the payment connector.
Our questions are:
Why is there a 200 character limit?
How can we extend the in-use string length of a property field beyond the 200 character limit?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
We recently found out by accident, that the standard EFT service implementation limits the length of (secure) string type parameter properties to 200 characters.
We're using connection strings and have implemented logging into Azure Application Insights and use the appi connection string as a payment processor parameter property.
Microsoft recently changed the contents of the Application Insights connection string to include the Application Id in it.
Previously the connection string was formatted in a way which didn’t exceed the maximum string length of 200 characters.
When you use the new type of connection string as a payment processor parameter property, it's truncated by D365FO in a way that breaks the connection string usage since the contents is missing the better part of the ApplicationId. Entering the value seemingly works just fine, you can paste the connection string value to the property field.
But after saving the changes, like said, the system truncates the string value to a maximum of 200 characters. When you pull the connection string property for use, it shows the first 200 characters of the actual connection string. The last part of the connection string is broken since it was truncated and does not contain the last delimiter and a value part.
Using the truncated connection string results in an error situation and prevents using the payment connector.
Our questions are:
Beta Was this translation helpful? Give feedback.
All reactions