Ir al contenido principal

Como actualizar los índices de búsqueda

 FUENTE ORIGINAL: https://www.sagecity.com/us/sage_erp_x3/b/sageerp_x3_product_support_blog/posts/how-do-you-update-the-search-indexes

How do you Update the Search Indexes?

Hey, Hey Readers,

Today we are going to cover how to update search indexes in Sage X3. Search index is one of those things no one really looks into much. It controls the search bar and its criteria on the top right of the screen. This search bar can be used to look up just about anything in the system, as long as the index is up to date. The index is controlled by the Elasticsearch component install (in v12 its just a separate download) and in conjunction with the Syracuse the data index gets its initial population. Every now and then someone will update it but only when absolutely necessary so it’s rare for us to see issues with it. You can also set it on a reoccurring update with the automated scheduler if you never want to worry about it.

So, some reasons you would want to do this? Or care to? If you use the search box to, well search for stuff. Maybe you added a bunch of features to the system, and you want to use the search box to search for them. Or you have a heavily modified the system and you want more accurate searches. OR…

I’m sure there is probably a TON more reasons why people would update indexes but then again, I don’t want to spend my day listing them out. Anyways, I am going to run through a quick demonstration on how you would manually update the Index.

First things first, you’re going to need the X3 Admin account to do this. Or a login that has access to the administration module (because that’s where we’re going). Get that account and log into X3. To update the indexes, you do not need to kick out any users. The index will automatically apply to all users once it finishes updating. You’ll want to navigate to the Search Index Management function under Administration Module then Usage sub menu.

Once the function loads it should look like this:

The Search Index Management function allows you to set what is indexed for searching. The Entities field allows you to select what is to be indexed as searchable. Blank = everything. You can also select to have the current index deleted before running the update so that you can get a brand-new index. You can read more about the Search index options HERE.

So, from here you can simply press the update index button and start the updating process to update the current index

After you click Update Index it should give you a popup like this (below) and start the updating process.

When it finishes, the popup will change to this (below) to signify that it completed. If there were any errors, it will list them in the text box at the bottom. You can also get a full scale look at the logs by clicking the paper looking icon  .

Now that it is done, you can test it out by using the Search Box in the top right and try to search for something

 

If it worked correctly, you should get search results like mine. ( I did a search for sales order).

 

And that’s all there is to it.

Until next time…

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 ,  ...
Leer más

How to create an additional line text (ACLOB) on purchase orders for internal notes

Sin conexión Kyle Klinger hace 1 día Origen:  https://www.sagecity.com/support_communities/sage_erp_x3/f/sage-x3-general-discussion-forum/143870/how-to-create-an-additional-line-text-aclob-on-purchase-orders-for-internal-notes I was trying to add internal notes to the purchase orders at a line level and was thought I would share a how to.  If you have a better way, please share.     Add column to PORDERQ; YLINTEX2, Type TXC   Save and validate table This is where the ID of the text will be stored at the record level, i.e. POQ~00000007, this is similar to field LINTEX  On screen POH2 Add column YLINTEX2, to Block 1. Most likely you will want this field to be hidden. On column NBLIG add a button action ACLOB2, description "Text internal" This button action will require an action parameter "CODE2", it will not be available until after save. Set the parameter "CODE2" to [M:POH2]YLINTEX2(nolign-2), the field that was just added....
Leer más

3 ways to send a mail from code in Sage X3, with more attachments too

Origen Fuente:  https://en.sagedev.it/sagex3/send-mail-from-code-with-attachments-sage-x3/ Autor:  https://en.sagedev.it/category/sagex3/ In this post I’ll show you how to send a mail from adonix code in Sage X3. The points we will face are: 1) Meladx/Send introduction 2) Sending  through  meladx (the best way for me: at the end with just a single code line you send a mail!) 3) Sending  through  Workflow 4) Sending  through  ENVOI_MAIL(…) From AWRKMEL Sending mail from code in Sage X3: Send vs meladx Sage X3 has two native ways for sending mails. The first way is  meladx  executable file, that you can find in  runtime\bin  directory. The seconde one is Send instruction, that was used to send mail through an application of the client station (for more information on “Send GSERMES”  go here ). The Meladx executable Meladx send messages through SMTP/POP3 protocols by means of the mail  ...
Leer más