I have a follow up question to make sure I understand this. To recap: - I've added a field to APR:Approver Lookup (creating an overlay), and want to use that field as part of the join criteria in a join form (SRS:RequestApproversLookup). - The system doesn't allow join criteria on overlays to be edited, so I am forced to edit the join in Base mode. - In order to use the field in the join criteria, I need to add it the join form.
The issue: - The new field on APR:Approver Lookup is not in the list of fields that can be added to the join form (when in Base Development mode.) - It IS on the list if I switch to Best Practice mode. Therefore (???): - The field on the underlying form needs to be added in Base Development mode Is that true? This small customization is getting me farther away from following best practices and I want to make sure I don't deviate any more than necessary. Thanks, Thad P.S. LJ - I re-read that entire section, and the table on page 131, it does list "Join qualification" in the "Can modify" column. Even though right next to it in the "Cannot modify" column it says "Join form information (cannot change underlying forms, join option, type, qualifier information)" On Wed, Sep 19, 2012 at 10:39 AM, Thad Esser <[email protected]> wrote: > Dang, there it is. I thought I searched that doc for the word "join" and > read everything it found. > > Okay, well, thanks for tracking that down for me, appreciate it. > > Thad > On Wed, Sep 19, 2012 at 10:28 AM, Longwing, LJ CTR MDA/IC < > [email protected]> wrote: > >> Thad, >> No ticket needed. This is by design. On page 131 of the Application >> Objects Guide, in the 'things overlays cannot do' section for forms it >> states >> >> - Application Owner (do not change the inclusion or exclusion of form in >> a deployable application) >> - Display-only form information (type) >> - Join form information (cannot change underlying forms, join option, >> type, qualifier information) >> - Name >> - Origin fields (cannot delete) >> - Unique index >> - Vendor form information (cannot change the associated plug-in, table >> name, type, vendor name) >> - View form information (type, table name, key field) >> - Views (cannot delete) >> >> So....obviously the important one is the third bullet. >> >> -----Original Message----- >> From: Action Request System discussion list(ARSList) [mailto: >> [email protected]] On Behalf Of Thad Esser >> Sent: Wednesday, September 19, 2012 11:11 AM >> To: [email protected] >> Subject: Re: Dev Studio 7.6.04 - Can't update join criteria >> >> ** >> LJ, >> >> I was hoping it was something simple that didn't require a BMC ticket, I >> guess I'll do that. >> >> The SRM:Request form was already overlaid due to other changes. I had to >> overlay the view on the join form to add the field from the underlying form. >> >> Thanks for the info, >> Thad >> >> On Wed, Sep 19, 2012 at 10:03 AM, Longwing, LJ CTR MDA/IC < >> [email protected]> wrote: >> >> >> Thad, >> I don't have a 7.6.4 system to work with at the moment, but... >> >> You obviously needed to Overlay APR:Approver Lookup to add the >> field, but you shouldn't need to overlay the SRM:Request form at all. You >> certainly need to overlay the join form, but being you aren't making >> changes on a particular view, I wouldn't expect that view needs to be >> overlaid, but then again, I'm not sure if the results list is view >> dependent or not. The Join Qualification certainly isn't view dependent, >> so I wouldn't expect the view to need to be overlaid to modify this....so >> I'm out of ideas as well. While I don't agree that you should go into base >> mode, I'm not sure what else to try (other than contact BMC of course). To >> answer your question to Ravi regarding the 'are there things', yes. You >> cannot overlay 'data'. Data would be applications, flashboard definitions, >> etc...this stuff at the moment MUST be modified in base development mode >> instead of Best Practice. >> >> >> -----Original Message----- >> From: Action Request System discussion list(ARSList) [mailto: >> [email protected]] On Behalf Of Thad Esser >> Sent: Wednesday, September 19, 2012 10:42 AM >> To: [email protected] >> Subject: Dev Studio 7.6.04 - Can't update join criteria >> >> >> ** >> >> Hello, >> >> I know I'm missing something simple, but being new to Dev Studio, >> I'm not sure where to look. I am trying to update the join criteria on a >> form, and dev studio isn't letting me. From the Form Propteries > Join >> Information window, I can select the text of the join qualificatin, but >> can't type in the text box, and the "..." button is disabled and doesn't >> respond to clicks. >> >> The join form has been overlaid (both form and view), as well as >> both of the underlying forms. >> I am in Best Practice Customization mode. >> I didn't see anyting in the docs that explicitly stated I >> couldn't do this. >> >> I'm not sure if it matters, but the forms involved are: >> Underlying forms: >> APR:Approver Lookup <-- added field >> SRM:Request >> Join form >> SRS:RequestApproversLookup <-- added the new field from >> APR:Approver Lookup, need to update the join to account for it. >> >> Using Dev Studio 7.6.04, SP4. (was on SP3 and it didn't work >> there either) >> >> Thanks, >> Thad >> >> _attend WWRUG12 www.wwrug.com <http://www.wwrug.com/> ARSlist: >> "Where the Answers Are"_ >> >> >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org < >> http://www.arslist.org/> >> attend wwrug12 www.wwrug12.com <http://www.wwrug12.com/> >> ARSList: "Where the Answers Are" >> >> >> >> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ >> >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" >> > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
