copy to

[omni]

Roger,

What are the character restrictions on the copy file...to ....


There is one client that has a customer the requires their reference number be the file name (.pdf).
All sort of odd reference number, including ones with multi-word, so spaces. Latest to kick out has one with a date 01/31/22 as the reference. Do not think it liked the slashes Think the current file name allowances are a lot different than they used to be.
We changed to dashes to test it out and all the invoice emails went out. We can create files with straight copy commands that work, that will not with the copy file. All this for one bill-to customer..geeze.

(we had already removed quite a few, such as ',', '&', '#',etc by just skipping by them)


Fred
Omni

[Wolfgang Ciriack]

Forbidden for file names are
#&"{}/\~%<>:?*

[k-insis]

Generally this is what you should read:

https://docs.microsoft.com/en-us/window ... ing-a-file

and "/" is not allowed. But you can mitigate that with replacing "/" in date with "-" easily.

Look under chapter "Naming Conventions" that includes list of restrictions.

Roger,

What are the character restrictions on the copy file...to ....


There is one client that has a customer the requires their reference number be the file name (.pdf).
All sort of odd reference number, including ones with multi-word, so spaces. Latest to kick out has one with a date 01/31/22 as the reference. Do not think it liked the slashes Think the current file name allowances are a lot different than they used to be.
We changed to dashes to test it out and all the invoice emails went out. We can create files with straight copy commands that work, that will not with the copy file. All this for one bill-to customer..geeze.

(we had already removed quite a few, such as ',', '&', '#',etc by just skipping by them)


Fred
Omni