Excel macros are not directly replicated when creating GT documents. On the other hand, there are great chances that the functionalities which you had developed in your macros are directly available in Gathering Tools – and without having any more code to write.

In fact, Excel macros can be broadly classified into two families:

“Client” oriented macros

The client-oriented macros are generally used to make the exchange processes more reliable (for example: prevent the user from modifying certain cell ranges, from creating invalid data, from saving a document if it does not obey certain rules, from saving it in a specific directory with a specific name, etc.). All these operations are natively ensured by Gathering Tools :

• GT documents are natively non-modifiable for users. They can only consult them and add data on the areas that are assigned to them. These areas can be completely dynamic.
• The transmission of information in GT does not involve sending a file: users have access to discussion threads in which the documents published are available for them. From the thread, they can consult the documents and transmit their data. The transmission will only be authorised if the data provided correspond to the management rules implemented during the configuration.
• The GT publication system automatically manages archiving, versioning and traceability.

Server-oriented macros

Server-oriented macros are generally used to manage data from the various Excel workbooks involved in the process (e.g., copying ranges of cells containing data entered by users and pasting them into “technical” sheets where they will be reorganized for use by another workbook or third-party tool). Again, these operations are natively handled by Gathering Tools :

• Data entered by users are automatically reorganized using the document compartments for integration into the database. From the database, it is automatically available for GT workflows or your third-party tools.
• If required, you can perform any type of data transformation using SQL actions, which can themselves be fully automated to be triggered by a predetermined event using triggers or our API.

(See the article: Are all Excel functionalities reproduced?)