Closed Solrosy closed 3 years ago
Hi,
since this information is part of the master data in the DSFinV-K, we want it to be centralized at only one point. That's why it is not possible to pass that data in the requests and should be changed manually in the portal.
Maybe we can feed it in via some other automatic method then?
Markus E. Gruber notifications@github.com schrieb am Mi. 16. Sept. 2020 um 09:51:
Hi,
since this information is part of the master data in the DSFinV-K, we want it to be centralized at only one point. That's why it is not possible to pass that data in the requests and should be changed manually in the portal.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/fiskaltrust/interface-doc/issues/114#issuecomment-693238332, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOQ6M75SRICIRBJX3XWIGPLSGBVBFANCNFSM4RMUBAGA .
-- Vom Handy gesendet
Hi @Lorscheidt,
thank you very much for reaching out. As @MarkusEGruber we will not allow to send these settings directly to the Middleware as we have several mechanisms that depend on this kind of information.
As far as I understood your concerns are mostly about the fact that doing the work in portal is erroneous and especially if there are many possystems, it is pretty exhausting do add all of them.
Just to be precise on the area that we are talking about: You are referring to the process described in this article: https://docs.fiskaltrust.cloud/doc/portal-manual-doc/doc/handbook-general/possystems.html
Do you think it would be enough if there is a similar option as for inviting posoperators or creating outlets available that let´s you import possystems through a CSV?
Thanks for helping us improve our products :)
Hi Fiskaltrust team,
We suggest to allow us sending the product information and software version in requests we pass on. It's tedious to do this manually in the portal. It's easier to manage and 100% correct this way.