The indexing of coalesce fields in a transform map is included in an update set?

[Peda]

Hi everyone,

I have multiple transform map for a ldap import, but I forgot to index the coalesce fields and want to know if I can click on Index Coalesce Fields link and the indexing of the database is then included in an update set? So that I can then stage the US with the index on other instances?

Thanks for your help.

[Michael Jones - · Accepted solution]

It has been my experience that when you click that link, if no index exists, you will see a pop-up that will indicate that it may take a while: 

Then once you click ok: 

The index has always been included in my update set, using this approach. That is to say, the definition for the index is included (sys_index), but not the actual index itself, if that makes sense. 

I hope this helps!

If this was helpful or correct, please be kind and remember to click appropriately!

Michael Jones - Proud member of the CloudPires team

[Peda]

@Michael Jones - CloudPires Thanks for reply,

so the defintion is in the update set and the actual index not? Can you descripe the different between index defintiion and actual index?

So I have to repat all steps on the other instance too or  what are you trying to say?

[Michael Jones -]

The definition is the entry on the sys_index table and defines the elements that will be used in the index. 

The index is created in the database itself and is not something that you can see within the instance. In insert of the record in the sys_index table is the trigger for the database to create the index.

You would not need to repeat anything; create the index in DEV and then deploy your update set. The index will be created in each environment but won't be available immediately (will take some time to generate in the background). 

I hope this helps!

If this was helpful or correct, please be kind and remember to click appropriately!

Michael Jones - Proud member of the CloudPires team