Daniel Delgado Candia

Certainly! Here's a longer and rephrased version of your request:

I am seeking support for the Brazilian localization, particularly concerning the NFC-e (Nota Fiscal de Consumidor Eletrônica) on CPOS (Cloud Point of Sale). At present, there is no functionality available to make the necessary calls with the fiscal localization. This support is essential for this region to fully utilize the out-of-the-box capabilities of Dynamics without resorting to custom code solutions. Implementing this feature would significantly enhance the usability and compliance of the system in Brazil, ensuring that businesses can operate efficiently and adhere to local fiscal regulations.

I am seeking support for the Brazilian localization, particularly concerning the NFC-e (Nota Fiscal de Consumidor Eletrônica) on CPOS (Cloud Point of Sale). At present, there is no functionality available to make the necessary calls with the fiscal localization. This support is essential for this region to fully utilize the out-of-the-box capabilities of Dynamics without resorting to custom code solutions. Implementing this feature would significantly enhance the usability and compliance of the system in Brazil, ensuring that businesses can operate efficiently and adhere to local fiscal regulations.

I would like to propose the idea to allow the customer number sequence creation in Manual for B2B Ecommerce prospects creation. Right now, according to Microsoft documentation this has to be set to Automatic, while setting this to Manual is returning an error with the following message: "Customer number sequence set to Manual. Customer could not be created"

We prefer to keep in control the customer creation process, our AR team has been doing this for a while but for B2B scenarios is not possible.

Thanks!

I would like to suggest that initial loyalty balances can be imported into the system without customization, right now the initial balances can't be imported directly into the system, they are in the posted status but not being reflected in the loyalty adjustments, for now creating a custom entity seems to be the most viable solution.