Ideas
New

Transcribe Import/Export (GESAOR) - External Code cannot have Spaces

The import transcriptions are very helpful when integration external systems with X3 using the import templates.

One limitation that I've encountered is that when defining the external code in the table it doesn't allow for spaces.

This has proved to be a limiting factor in its use on a couple of occasions.

What is the design consideration here to prohibit the use of spaces in the external code?

Could R&D relax this constraint and allow for spaces in the external code?

Thanks,

Kevin