Upload mInventory preset Configuration Spreadsheets Using RACE™

RACE™ configurations are provided in spreadsheets. Upload the spreadsheets in RACE™ to enable the latest mInventory features.

When you upload the RACE™ pre-set configuration spreadsheets, you enable all the recommended features / configurations automatically. Contact your Innovapptive representative for these spreadsheets.

mInventory configuration RACE Spreadsheets

  • Admin_Configurations: (Mandatory file). This file contains configurations for UI Field Type, Components, Form Attributes, System ID, DD Tables, Barcode Types, and Attachment Destination.
    Note:
    • If UI field type is related to drop down, check and maintain dynamic drop-down configuration fields data properly (DD TABLE NAME, DD FIELD NAME, TEXT REQ, TEXT TABLE NAME, TEXT FIELD NAME, TEXT KEY FIELD NAME, DEPENDENCY FIELD NAME, DEPENDENCY KEY FIELD NAME).
    • Try to avoid Transaction tables in DD Table Name (MARA, VBAK, MARC, MSEG).
    • Dynamic drop-down table should have very less data (< 1000 entries). If we have more data in dynamic drop-down table, there will be chances of offline store failure.
  • mInventory_Configurations: (Mandatory file) This spreadsheet contains configurations for Scoping, Screen Configurations, Extensions, Data Configurations, UI Labels, GIS Maps, Modules and Screens, and Search.
    • Data Configurations: The configurations in the sheet ensure that the performance of application is optimized.
      Note:
      • Sync the collections to offline as per the customer scope only.
      • For drop-down collection, if no. of entries < 1000, then enable delta token and offline sync. Access from offline should be active.
      • For drop-down collection, if no. of entries > 1000, then enable skip token and offline sync. Skip token size should be 500 to 1000. Access from offline should be active.
      • For expand collections, enable skip token and offline sync. Access from offline should be active.
      • Delete any duplicate collections.
      • If expand collection (GRPOHeaderCollection?$expand=GRPOItemCollection plain collection : GRPOHeaderCollection...etc.) is enabled for offline sync, then there is no need to enable the offline sync for plain collection (GROPHEADERCOLLECTION). We maintain expand collection and plain collection separately only to increase the skip token value in online mode.
    • App Scoping: The sheet contains all the mInventory Modules.
      Note:
      • Each entry should have a system name.
      • Do not configure any static feature directly in customer environment. Check with RACE development team.
      • Do not maintain any junk data.