The current approach for fiscal integration does not allow to manage fiscal printer's IP address in proper way in large scaling deployment scenarios. The current design to have Technical profile specified in POS Hardware profile results into:
- Changing hosts file in Windows operation system on every machine which requires separate profile per machine, and high cost of maintenance from OS point of view, OR
- Having Retail Hardware profile per fiscal printer, which means Retail Hardware profile per every registry which means hundreds of the hardware profile to manage in D365.
Moreover, the current design does not align to standard approach to configure IP address for a device for registry in specific form “IP address configuration” at Retail/Channel Setup/PoS Setup/Registers/<Register tab> - <Configure IP addresses>
The design must be changes to the standard design and the IP address of the fiscal printer should be configured in this IP addresses configuration form. mPOS should be able to get this configuration for fiscal printer from there and use it accordantly.
That allows to avoid significant drawbacks for hosts file or hardware profiles mentioned above.
Administrator on 3/28/2023 3:21:00 PM
Thank you for your thoughtful suggestions. Given that there is a workaround for this shortcoming, we need to prioritize other work for which no workaround or extensibility option exists, and thereforew won't be able to get to this for the foreseeable future.