Related tables in CMS010 for use by CMS100MI

I'm developing an H5 app that's using Info Brower Categories via CMS100MI. One of the categories that I need to create relies on data stored in CUGEX1 which needs to be related to another CUGEX1 FILE category. If I attempt to define my Info Browser Category with CUGEX1 as the master table and CUGEX1 as a related table then M3 Cloud gives me an error telling me that the table is invalid. I'm guessing there's a limitation that doesn't allow the master table to be related to itself. Can anyone confirm whether that's the case and if it is can anyone think of a work around.

Find more posts tagged with

API Usage

Accepted answers

All comments

Maxime Richard

Hello,

Correct. Not possible to add a related table in CMS011 that is the same as the FILE field in CMS010.

So you need a CUGEX for CUGEX 1? You can add CUGEX2 or 3 as related tables but this requirement seems strange (need to set up CMS080 before).

Legacy Contributor

Thanks Maxime,

We have data rows being stored in CUGEX1 that includes a category code. This is custom data so not an extension of any M3 table and is being maintained via CUSEXTMI. What I'm looking for is a means of maintaining the category list and then joining to the data in the Info Browser Category. I was assuming I'd need to use CUGEX1 for the categories and they'd be maintained via the H5 app calling CUSEXTMI with a custom FILE value. This seemed fine until I realized I couldn't related CUGEX1 with one FILE value to CUGEX1 with a different custom FILE value. Is there a better way of doing this given neither the data or the categories are stored in standard M3 tables? It's effectively a piece of bespoke functionality using M3 generic extension as the data store.

Legacy Contributor

If I move my categories to CUGEX3 then that will solve 90% of my problem. It'll allow me to relate CUGEX1 and CUGEX3 to join my data to the categories.

Copyright © 2025 Infor. All rights reserved.