Hi, We are setting up our vendors in the Purchasing Module and I was told that using Characters such as "&" or "_" would pose a problem in GP. I wasn't told specifically what problems it would create. Can someone tell me if this is true and what problems it would produce?
*This post is locked for comments
Yes. I agree with above valuable suggestion. I would like to avoid special charter in GP. Because, if you integrate GP with other application. It may through error.
Suppose, if you are using "&" symbol in GP account Category Setup then trying to map the category in Management Reporter, it will not support. Because Management Reporter consider "&" symbol as addition operation. So, better you can avoid the special character in GP.
Hope this helps!!!
Please Verify this answer if it has been useful to you. This could help others trying to solve the same or similar problem.
I agree with Harry and Leslie. I would avoid the use of special characters in 'IDs'. I recall having a problem with a batch ID in GP 2010 which was using special characters.
Even though many GP default security Task IDs use "_" and "*" there is not guarantee that any 3rd party module will cope with them.
One other thing occurred to me after my initial post. Just because Dynamics GP supports the use of special characters does not mean this is a best practice. Dynamics GP is frequently integrated with other products and tools, and there are definitely no guarantees special characters will be supported universally. The benefits of using special characters must be weighed against the potential for integration with other system, and any necessary efforts required if special characters are not supported.
Using special characters is not prohibited by Dynamics GP. Here is a link to an earlier post on the topic.
community.dynamics.com/.../85445
That being said, I am fond of using Macros to update records in Dynamics GP, and the use of single quotes A.K.A apostrophes in fields can cause some wrinkles when Macro's are used. In SQL data is usually bounded by single quotes (i.e. Select * from PM00200 where VENDORID = 'ODOULS') So, using O'DOUL'S, instead would create problems because 'O'DOUL'S' would appear as 'O' DOUL 'S' to a macro. I would council against using the special character ' for this reason.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (