Skip to main content
Solved

adding an index to an existing entity

  • September 21, 2026
  • 2 replies
  • 36 views
Hero (Customer)
Forum|alt.badge.img+11

Hi

Please can anyone clarify what would happen if we added an index to an existing entity by adding a .storage file with the new index in IFS Developer Studio?

Is this actually the correct way to add a new index?

Will the new indexing be generated for existing data when the entity is deployed from IFS Developer Studio?

Will the new indexing be generated for existing data when the deployment containing the new file is done for a different environment from Build Place?

Thanks,

mmck

Best answer by Esther San Segundo

Hi ​@MMcK . Just creating the .storage file with the new index defined in it, is not enough. Please check technical documentation:

https://docs.ifs.com/techdocs/26r1/060_development/027_base_server_dev/007_concepts/090_source_code_file/storage_files/ 

“This file type is not directly deployable into the database and has to pass through the code generator which produces database deployable CRE files.”

You will need to generate the code for your entity on the IFS Developer Studio. This will create a .cre file. Copy the code around the deployment of the new index and:

  1. Add a new .cdb file and prepare here its content with the creation of the new index.
  2. Or if you are on 25R2 or higher with your customizations already compatible with Delivery continuity, place this content in the existing .ddlsource file, or create it if necessary. DDLSOURCE files.

Check the results of your code changes by ordering a topic environment on the Build Place. In this way you’ll be sure the code is deployable and works as expected.

2 replies

Esther San Segundo
Sidekick (Employee)
Forum|alt.badge.img+6

Hi ​@MMcK . Just creating the .storage file with the new index defined in it, is not enough. Please check technical documentation:

https://docs.ifs.com/techdocs/26r1/060_development/027_base_server_dev/007_concepts/090_source_code_file/storage_files/ 

“This file type is not directly deployable into the database and has to pass through the code generator which produces database deployable CRE files.”

You will need to generate the code for your entity on the IFS Developer Studio. This will create a .cre file. Copy the code around the deployment of the new index and:

  1. Add a new .cdb file and prepare here its content with the creation of the new index.
  2. Or if you are on 25R2 or higher with your customizations already compatible with Delivery continuity, place this content in the existing .ddlsource file, or create it if necessary. DDLSOURCE files.

Check the results of your code changes by ordering a topic environment on the Build Place. In this way you’ll be sure the code is deployable and works as expected.

    Hero (Customer)
    Forum|alt.badge.img+11
    • MMcK
    • Author
    • Hero (Customer)
    • September 22, 2026

    Hi ​@Esther San Segundo 

    Many thanks, yes, of course, I should have remembered the .cre and .cdb files when deploying through IFS Developer Studio.

    Many thanks for confirming.

     

      Terms & ConditionsAccessibility statement