Ir al contenido principal

How to Install and Manage Sage X3 Add-Ins in Microsoft Office

When you enable an add-in, it adds custom commands and new features to Microsoft Office programs that help increase your productivity. In this blog post, we’ll review how to install the Sage X3 Add-In for MS Excel and what to do if your Sage X3 Add-In is missing.

Fuente original: https://www.netatwork.com/how-to-install-and-manage-sage-x3-add-ins-in-ms-office/

How to Install the Sage X3 Add-In in Microsoft Excel

Go to Administration > Utilities > Installation > Install addins for Office

V11 Image:

How to Install and Manage Sage X3 Add-Ins in MS Office

 

V12 Image:
How to Install and Manage Sage X3 Add-Ins in MS Office

 

It should begin downloading the exe, open the exe Next > Install

How to Install and Manage Sage X3 Add-Ins in MS Office

 

Open Excel > File > Options

How to Install and Manage Sage X3 Add-Ins in MS Office

 

Select Add–Ins > Manage: COM Add-ins > Go

How to Install and Manage Sage X3 Add-Ins in MS Office

 

Check the “Excel AddIn for Sage” > Ok

How to Install and Manage Sage X3 Add-Ins in MS Office

 

You are now ready to export Excel-based reports/grids from Sage X3.

How to troubleshoot and fix a missing Sage X3 add-in in Microsoft Excel

Open the Microsoft Office product where the Sage X3 add-in is missing.

Go to Options:

Fix Missing Sage X3 Add-Ins in MS Office

Select Add-ins:

Fix Missing Sage X3 Add-Ins in MS Office

If Sage X3 appears on the list of Disabled Application Add-ins, select Manage: Disabled Items and press GO:

Fix Missing Sage X3 Add-Ins in MS Office

 

Fix Missing Sage X3 Add-Ins in MS Office

 

Choose SyracuseExcelAddIn from the Disabled Items list and press Enable:

 

Fix Missing Sage X3 Add-Ins in MS Office

 

Then choose Manage: COM Add-ins and press GO:

 

Fix Missing Sage X3 Add-Ins in MS Office

 

From the list of available COM Add-ins, check Excel Addin for Sage ERP X3 and press OK:

 

Fix Missing Sage X3 Add-Ins in MS Office

 

Press OK on Excel options.


Sage X3 Tips

You will now see the Sage Add-in on the ribbon. If you do not you may need to close and re-open application.

If you have any issues following these steps or need additional help enabling missing Office add-ins, please contact us.

Entradas populares de este blog

Valores de fstat

Fstat fstat  is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction. Syntax fstat Examples # MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL # Create a record in the table MYTABLE with they key value 1 if it doesn't exist Local File MYTABLE [MYT] Read [MYT]KEY1=1 If fstat [MYT]KEYVAL=1 : Write [MYT] If fstat MSG="The key was created in the mean time" Else MSG="Key created" Endif Else MSG="Key already exists" Endif Details fstat  is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  ...

SAGE X3 SILENT IMPORT (IMPORTSIL) WITH ERROR CATCHING

FUENTE ORIGINAL: https://pluginx3.com/en/blog/post/sage-x3-silent-import-importsil-with-error-catching.html You already know how to manually generate a CSV file in order to import it threw a template in Sage X3. But If you wonder how to catch detailed errors after a silent import here is the solution. Sometimes you need to catch the incoming errors in order to alert the end-user regarding an issue. Closed period, wrong date etc …. Unfortunalty the standard Sage X3 silent import function doesn’t natively show the detailed errors during the import process. Call IMPORTSIL([M:IMP2]MODIMP,[M:IMP2]NOMIMP) From GIMPOBJ And the standard function ERR_IMPORT will only show the overall status of the importation and not the detailed errors. IMPORTSIL function is pushing all the log data into a tracefile in order to avoid any popup on end-user screen. So you have a log file available in order to search for errors in it. Sage X3 runtime is using the same principals standards as any shell for log...

Sage X3 Create a new CLOB Text

Here how to create a CLOB text Funprog F_CRELOB ( YABRFIC , YTEXTE ) Value Char YABRFIC Value Char YTEXTE Local Char XXRTFTXT ( 250 ) ( 3 ) XXRTFTXT ( 0 ) = "{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 MS Sans Serif;}}\viewkind4\uc1\pard\f0\fs17 " XXRTFTXT ( 1 ) = YTEXTE XXRTFTXT ( 2 ) = "\par}" Local Char X_RET Local Integer XXOK Local Char XCHAMPLIEN : XCHAMPLIEN = "YYYY" Global Char YYYY : YYYY = YABRFIC Local Clbfile WWCLOB Local Mask ACLOB [ M :ACL ] Setlob WWCLOB With XXRTFTXT [ M :ACL ] CLOB = WWCLOB Call CRE_CLOB_ACL ( XCHAMPLIEN , XXOK ) From TRTX3TEX Close Local Mask [ M :ACL ] X_RET = YYYY Kill YYYY End X_RET