integration:nhlmis

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
integration:nhlmis [2026/06/09 14:21] – [Synchronising items] Gary Willettsintegration:nhlmis [2026/06/09 14:25] (current) – [Synchronising items] Gary Willetts
Line 108: Line 108:
   * if it has a Generic parent ID which is different from its ID then it is created as an NHLMISChild property of the parent item (as long as it doesn't already exist as this property!) with a value of "//item code//,pack_//pack size//" e.g. "ghsc-mal0004,pack_100".   * if it has a Generic parent ID which is different from its ID then it is created as an NHLMISChild property of the parent item (as long as it doesn't already exist as this property!) with a value of "//item code//,pack_//pack size//" e.g. "ghsc-mal0004,pack_100".
  
-In addition, new items will be added to master lists that have tags matching the item's program name (master list tag format is "NHLMISProgram://program name//"). If the master list does not exist then it will be created by mSupply.+In addition, new items will be added to master lists that have tags matching the item's program name (master list tag format is "NHLMISProgram://program name//"). If the master list does not exist then it will be created by mSupply. The master list can then be used to make the item visible in the correct stores (either manually or automatically if the preference to manage item visibility by master lists is turned on and the program master lists are already assigned to the correct stores).
  
 The pack size sent with an item is set as its default pack size. The pack size sent with an item is set as its default pack size.
  • Last modified: 2026/06/09 14:25
  • by Gary Willetts