Looking for suggestions on how to add a search parameter to the Product search that will include multiple fields.  The use case is that users want to be able to click add product to an Opportunity and search one parameter that includes the Family, name and description fields.

My thoughts so far:

• Create a view that does a concat on these three fields.  (Having trouble adding a view as a searchable parameter)


• Build a SQL job that refreshes a table that holds the full product names and product ids for all products (Messy option reliant on SQL job)


• Create a calculated string on the product entity that combines these fields (not sure how to create or concatenate from the properties window in Application Architect)

I did see a post on adding a table in SLX manager and then removing it and creating a view of the same name.  I haven't tried this one but it seems a little hacky for a production environment

Thanks for any help you guys can provide.  I'll cross post to the infor communities site but IMO this forum is way more useful!

(edit) We are running 8.3 v9 on the web client only.

We're using 7.5.4 Web but maybe this helps.

I've had a similar problem, but I had to concatenate values of the same field of different objects of the same entity since they can be related to each other. To solve this issue, I added a new Business Rule returning the concatenated string and call it from within the On...Insert and On...Update Events of this entity. Whether to use OnBefore... or OnAfter... depends on when you have the required information available (since the Id can only be used after inserting the object). The Business Rule has to be called OnInsert and OnUpdate since the OnUpdate-Event does not get fired on inserting.

Another thing is (still only 7.5.4 knowledge) that you can only lookup fields defined under the Layout tab in the group builder dialog. And even then, every user can set its own "Default lookup Layout" for each entity. But since you can link any tables to each other via Local Join, it's possible to search for fields being delivered by a view (so this might be something for your first idea). Of course the view has to be designed in a way that it can be uniquely linked to the entity in question.