Solved

IFS Apps 9: Custom Fields in Document Management Macros?

  • 16 September 2020
  • 2 replies
  • 421 views

Userlevel 5
Badge +8

We use a Document Management Marco in IFS, to enable DocumentProperties/QuickParts in Microsoft Word and Excel documents. This macro allows data held in IFS (e.g Document Number, Revision Number, Title, etc) to be automatically inserted into the Word or Excel document. We have added a custom field in IFS, and I need to automatically insert the data from that custom field into the Word Document.

On the “Macro Basic” screen, “Object Attributes for Macro” tab we have to list all the IFS fields applicable to a given Object, which shall be made available to the macro code, but it seems to be limited to out-of-the-box fields only. Is there any way to add a custom field?

Note: I am aware that in IFS Apps 10, this functionality has been expanded to allow custom fields to be used, but we really need to be able to do this in Apps 9.

icon

Best answer by paul harland 16 September 2020, 13:44

View original

2 replies

Userlevel 7
Badge +24

Not sure if this will help you Robin, but if you go into the Object Connections page there’s a column for ViewName - you can make sure the custom field view is mentioned there e.g. customer_info_CFV, instead of customer_info.  This will make the custom fields in that view accessible in the Object Attributes tab you mention.

But I think from your question, your custom field is on the document record? 

Userlevel 5
Badge +8

Thank you very much Paul, your answer solved my issue perfectly. In my original post I implied that it was a custom field on the Document Revision screen that we needed to access but that was just a simplification on my part. The documents in question will acutely be connected to a lot batch master, and it was a custom field on that screen that we needed access to. Changing the View on the “Object Connection” screen to point at LOT_BATCK_MASTER_CFV allowed me to add the custom fields on the “Object attributes for macros” screen, and after that it was just a case of setting up the template document to pick up the required field.

Thank you very much for your help!

Reply