This topic was recently discussed on communities https://communities.bmc.com/message/583802#583802
They obviously 'know' that the duplicates exist...which aren't actually duplicates of course (different overlay) value....but yes...it's somewhat surprising that this is affecting their own workflow....the thing that's not surprising is that they didn't catch it....because they obviously don't create overlays of their own workflow :) On Tue, Feb 2, 2016 at 6:31 AM, Atul Vohra <a...@protechsoftwareinc.com> wrote: > ** > > In v9 (Linux), we created overlays of some main forms and are seeing that > in arschema table it created a new entry for the overlay table with the > same schemaid and name. > > > > So there are 100+ ALs, 17+ menus, and 1000+ filters which make select > calls to arschema to list fields or a field from a particular form (table). > This now returns duplicate fields - this can be resolved by using DISTINCT > but am surprised that this was not caught by BMC. > > We have called in BMC with this issue and so far they are fixing (i.e. > modify the AL and put the DISTINCT keyword) in various active links as they > debug the issue. > > > > Ex: We have an overylay of SRM:Request and now in the AP:Rule Definition > form , try setting variables for form = SRM:Request > > > > Anyone else facing the same issue. > > > > Thanks > Atul > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
