Generic Enquiry Conflicts - Velixo Reports for Excel and Acumatica (Financial Report Writer)

RE: Generic Enquiry Conflicts

Tim Rodman — Wed, 04 Jul 2018 20:35:28 +0000

I have noticed the same thing as Gabriel when using Velixo Reports in multiple environments. The ID for each inquiry is different in each environment, but Velixo Reports still works fine in each environment.

When I say ID, I mean the Screen ID like this:

RE: Generic Enquiry Conflicts

Gabriel Michaud — Wed, 04 Jul 2018 12:06:23 +0000

Hi Nic,

Velixo Reports accesses the inquiry by name. The ID is auto assigned by Acumatica when we deploy the inquiries and is not important for Velixo Reports. This is the first time I hear about conflicts with the inquiry IDs. I suggest deleting all the Velixo**** inquiries, and opening a report in Excel. You will be prompted to create them again.

Gabriel.

RE: Generic Enquiry Conflicts

AhmedBahar — Wed, 04 Jul 2018 02:38:33 +0000

Lazy development. Every vendor is supposed to stick to the initial that they were provided by Acumatica.

For example, I work Kensium and the GIs, Site Map entries, etc. are supposed to be starting with KN.XX.XX.XX.

This requires renaming and packaging the customizations with the new Site Map entries.

Velixo may be VE and Fusion is NOT supposed to be GIFR. They should be renaming their GIs and I've been preparing to send them a long explanation regarding this because their customization always conflicts and I have to do janitorial GI work...

Generic Enquiry Conflicts

Nwood — Tue, 03 Jul 2018 22:54:15 +0000

I have previously had Velixo installed to our demo system. Today I installed the new AcumaticaPOS (FusionPOS) customisation and found the Screen IDs for this customisation conflict with Velixo (GIFR******).

Given that both customisations are accessed by external applications I expect that this current conflict will prevent both applications being deployed to the same system.