Maximo List Archive

This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.



Display ORGANIZATION field in SR application

From: janice c (2012-03-12 06:46)

Hi all,
Need help guys, I'm using version 7116. I need to make the ORGANIZATION field visible in the SR application. Since SR is a system level application, I'm getting an invalid binding error when I try to use the existing lookup called ORG. Below are the textbox properties of ORGID field.

Attribute : ORGID
Lookup : ORG
Here is the xml of the org lookup, I'm just trying to use the existing lookup.
<table id="org" inputmode="readonly" selectmode="single">
<tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="org_lookup_tablebody">
<tablecol dataattribute="orgid" id="org_lookup_tablebody_col_0" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
<tablecol dataattribute="description" id="org_lookup_tablebody_col_1" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
</tablebody>
</table>
Any idea on how to resolve the invalid binding error? or is there any other way to do it? Thank you all.


From: Jason Verly (2012-03-12 17:43)

Do you still get an invalid binding when just adding the field ORGID, via App Designer, and leaving off the lookup?
--- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@...> wrote:
>
> Hi all,
>
> Need help guys, I'm using version 7116. I need to make the ORGANIZATION field visible in the SR application. Since SR is a system level application, I'm getting an invalid binding error when I try to use the existing lookup called ORG. Below are the textbox properties of ORGID field.
>
> Attribute : ORGID
> Lookup : ORG
>
> Here is the xml of the org lookup, I'm just trying to use the existing lookup.
>
> <table id="org" inputmode="readonly" selectmode="single">
> <tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="org_lookup_tablebody">
> <tablecol dataattribute="orgid" id="org_lookup_tablebody_col_0" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
> <tablecol dataattribute="description" id="org_lookup_tablebody_col_1" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
> </tablebody>
> </table>
>
> Any idea on how to resolve the invalid binding error? or is there any other way to do it? Thank you all.
>


From: janice c (2012-03-12 22:06)

Sorry about that, I get the invalid binding when I select value from the lookup.
Thank you.
--- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@...> wrote:
>
> Do you still get an invalid binding when just adding the field ORGID, via App Designer, and leaving off the lookup?
>
> --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> >
> > Hi all,
> >
> > Need help guys, I'm using version 7116. I need to make the ORGANIZATION field visible in the SR application. Since SR is a system level application, I'm getting an invalid binding error when I try to use the existing lookup called ORG. Below are the textbox properties of ORGID field.
> >
> > Attribute : ORGID
> > Lookup : ORG
> >
> > Here is the xml of the org lookup, I'm just trying to use the existing lookup.
> >
> > <table id="org" inputmode="readonly" selectmode="single">
> > <tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="org_lookup_tablebody">
> > <tablecol dataattribute="orgid" id="org_lookup_tablebody_col_0" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
> > <tablecol dataattribute="description" id="org_lookup_tablebody_col_1" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
> > </tablebody>
> > </table>
> >
> > Any idea on how to resolve the invalid binding error? or is there any other way to do it? Thank you all.
> >
>


From: Travis Herron (2012-03-13 14:19)

We don't use multi-org or multi-site, nor do we use the SR app, so I'm no expert on the subject; however --
Why would you use the lookup there? Are your users selecting the SITEID? Is Maximo already supplying the SITEID? When a value is supplied to SITEID, is a value for ORGID automatically appearing?
I guess what I'm trying to get at is I would think the SITEID is what's changing, MAYBE, and that the ORGID would come from that, and you'd only want to display it. And your original question was that you needed to "show" it on the screen. Does it HAVE TO be chooseable (because in the grand scheme of the software, I'm not sure it's designed to be chooseable)?
Nonetheless, I think the invalid binding problem is coming from ORGID lacking a validation class or a domain. If you really need to have the lookup working, go to Database Configuration, choose the SR object, move to the ORGID attribute, and try adding psdi.app.system.FldDomainOrgId as the class. Try in a test environment first, of course.
Travis Herron
--- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@...> wrote:
>
> Sorry about that, I get the invalid binding when I select value from the lookup.
> Thank you.
>
>
> --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> >
> > Do you still get an invalid binding when just adding the field ORGID, via App Designer, and leaving off the lookup?
> >
> > --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> > >
> > > Hi all,
> > >
> > > Need help guys, I'm using version 7116. I need to make the ORGANIZATION field visible in the SR application. Since SR is a system level application, I'm getting an invalid binding error when I try to use the existing lookup called ORG. Below are the textbox properties of ORGID field.
> > >
> > > Attribute : ORGID
> > > Lookup : ORG
> > >
> > > Here is the xml of the org lookup, I'm just trying to use the existing lookup.
> > >
> > > <table id="org" inputmode="readonly" selectmode="single">
> > > <tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="org_lookup_tablebody">
> > > <tablecol dataattribute="orgid" id="org_lookup_tablebody_col_0" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
> > > <tablecol dataattribute="description" id="org_lookup_tablebody_col_1" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
> > > </tablebody>
> > > </table>
> > >
> > > Any idea on how to resolve the invalid binding error? or is there any other way to do it? Thank you all.
> > >
> >
>


From: Jason Verly (2012-03-13 14:30)

I got the same invalid bind too when using the lookup. If you add 'MULTISITE' as the Go To application, I was able to return the value back to the SR app with no issues. I'm guessing that the SR app is having some issue recognizing the relationship back to the ORGANIZATION table.
Try adding a new relationship for the SR table back to ORGANIZATION.
--- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@...> wrote:
>
> Sorry about that, I get the invalid binding when I select value from the lookup.
> Thank you.
>
>
> --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> >
> > Do you still get an invalid binding when just adding the field ORGID, via App Designer, and leaving off the lookup?
> >
> > --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> > >
> > > Hi all,
> > >
> > > Need help guys, I'm using version 7116. I need to make the ORGANIZATION field visible in the SR application. Since SR is a system level application, I'm getting an invalid binding error when I try to use the existing lookup called ORG. Below are the textbox properties of ORGID field.
> > >
> > > Attribute : ORGID
> > > Lookup : ORG
> > >
> > > Here is the xml of the org lookup, I'm just trying to use the existing lookup.
> > >
> > > <table id="org" inputmode="readonly" selectmode="single">
> > > <tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="org_lookup_tablebody">
> > > <tablecol dataattribute="orgid" id="org_lookup_tablebody_col_0" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
> > > <tablecol dataattribute="description" id="org_lookup_tablebody_col_1" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
> > > </tablebody>
> > > </table>
> > >
> > > Any idea on how to resolve the invalid binding error? or is there any other way to do it? Thank you all.
> > >
> >
>


From: Jason Verly (2012-03-13 16:11)

FYI - Classfile fix worked in my test env.
--- In MAXIMO@yahoogroups.com, "Travis Herron" <therron@...> wrote:
>
> We don't use multi-org or multi-site, nor do we use the SR app, so I'm no expert on the subject; however --
>
> Why would you use the lookup there? Are your users selecting the SITEID? Is Maximo already supplying the SITEID? When a value is supplied to SITEID, is a value for ORGID automatically appearing?
>
> I guess what I'm trying to get at is I would think the SITEID is what's changing, MAYBE, and that the ORGID would come from that, and you'd only want to display it. And your original question was that you needed to "show" it on the screen. Does it HAVE TO be chooseable (because in the grand scheme of the software, I'm not sure it's designed to be chooseable)?
>
> Nonetheless, I think the invalid binding problem is coming from ORGID lacking a validation class or a domain. If you really need to have the lookup working, go to Database Configuration, choose the SR object, move to the ORGID attribute, and try adding psdi.app.system.FldDomainOrgId as the class. Try in a test environment first, of course.
>
> Travis Herron
>
>
> --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> >
> > Sorry about that, I get the invalid binding when I select value from the lookup.
> > Thank you.
> >
> >
> > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > >
> > > Do you still get an invalid binding when just adding the field ORGID, via App Designer, and leaving off the lookup?
> > >
> > > --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Need help guys, I'm using version 7116. I need to make the ORGANIZATION field visible in the SR application. Since SR is a system level application, I'm getting an invalid binding error when I try to use the existing lookup called ORG. Below are the textbox properties of ORGID field.
> > > >
> > > > Attribute : ORGID
> > > > Lookup : ORG
> > > >
> > > > Here is the xml of the org lookup, I'm just trying to use the existing lookup.
> > > >
> > > > <table id="org" inputmode="readonly" selectmode="single">
> > > > <tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="org_lookup_tablebody">
> > > > <tablecol dataattribute="orgid" id="org_lookup_tablebody_col_0" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
> > > > <tablecol dataattribute="description" id="org_lookup_tablebody_col_1" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
> > > > </tablebody>
> > > > </table>
> > > >
> > > > Any idea on how to resolve the invalid binding error? or is there any other way to do it? Thank you all.
> > > >
> > >
> >
>


From: janice c (2012-03-14 22:33)

Hi there! Thank you so much guys! I don't have the invalid binding anymore.
Cheers!
--- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@...> wrote:
>
> FYI - Classfile fix worked in my test env.
>
> --- In MAXIMO@yahoogroups.com, "Travis Herron" <therron@> wrote:
> >
> > We don't use multi-org or multi-site, nor do we use the SR app, so I'm no expert on the subject; however --
> >
> > Why would you use the lookup there? Are your users selecting the SITEID? Is Maximo already supplying the SITEID? When a value is supplied to SITEID, is a value for ORGID automatically appearing?
> >
> > I guess what I'm trying to get at is I would think the SITEID is what's changing, MAYBE, and that the ORGID would come from that, and you'd only want to display it. And your original question was that you needed to "show" it on the screen. Does it HAVE TO be chooseable (because in the grand scheme of the software, I'm not sure it's designed to be chooseable)?
> >
> > Nonetheless, I think the invalid binding problem is coming from ORGID lacking a validation class or a domain. If you really need to have the lookup working, go to Database Configuration, choose the SR object, move to the ORGID attribute, and try adding psdi.app.system.FldDomainOrgId as the class. Try in a test environment first, of course.
> >
> > Travis Herron
> >
> >
> > --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> > >
> > > Sorry about that, I get the invalid binding when I select value from the lookup.
> > > Thank you.
> > >
> > >
> > > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > > >
> > > > Do you still get an invalid binding when just adding the field ORGID, via App Designer, and leaving off the lookup?
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > Need help guys, I'm using version 7116. I need to make the ORGANIZATION field visible in the SR application. Since SR is a system level application, I'm getting an invalid binding error when I try to use the existing lookup called ORG. Below are the textbox properties of ORGID field.
> > > > >
> > > > > Attribute : ORGID
> > > > > Lookup : ORG
> > > > >
> > > > > Here is the xml of the org lookup, I'm just trying to use the existing lookup.
> > > > >
> > > > > <table id="org" inputmode="readonly" selectmode="single">
> > > > > <tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="org_lookup_tablebody">
> > > > > <tablecol dataattribute="orgid" id="org_lookup_tablebody_col_0" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
> > > > > <tablecol dataattribute="description" id="org_lookup_tablebody_col_1" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
> > > > > </tablebody>
> > > > > </table>
> > > > >
> > > > > Any idea on how to resolve the invalid binding error? or is there any other way to do it? Thank you all.
> > > > >
> > > >
> > >
> >
>


From: sdcosta (2012-04-27 16:22)

Thank you Travis your post helped immensely. We have a custom filed workorder.wo20 inherited from an old version of Maximo and the person lookup for this field worked on the WO details tab but gave an invalid binding on the advanced search. On reading your thread I associated psdi.app.person.FldPersonID class to workorder.wo20 and the invalid binding disappeared. Thanks kindly.
--- In MAXIMO@yahoogroups.com, "Travis Herron" <therron@...> wrote:
>
> We don't use multi-org or multi-site, nor do we use the SR app, so I'm no expert on the subject; however --
>
> Why would you use the lookup there? Are your users selecting the SITEID? Is Maximo already supplying the SITEID? When a value is supplied to SITEID, is a value for ORGID automatically appearing?
>
> I guess what I'm trying to get at is I would think the SITEID is what's changing, MAYBE, and that the ORGID would come from that, and you'd only want to display it. And your original question was that you needed to "show" it on the screen. Does it HAVE TO be chooseable (because in the grand scheme of the software, I'm not sure it's designed to be chooseable)?
>
> Nonetheless, I think the invalid binding problem is coming from ORGID lacking a validation class or a domain. If you really need to have the lookup working, go to Database Configuration, choose the SR object, move to the ORGID attribute, and try adding psdi.app.system.FldDomainOrgId as the class. Try in a test environment first, of course.
>
> Travis Herron
>
>
> --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> >
> > Sorry about that, I get the invalid binding when I select value from the lookup.
> > Thank you.
> >
> >
> > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > >
> > > Do you still get an invalid binding when just adding the field ORGID, via App Designer, and leaving off the lookup?
> > >
> > > --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Need help guys, I'm using version 7116. I need to make the ORGANIZATION field visible in the SR application. Since SR is a system level application, I'm getting an invalid binding error when I try to use the existing lookup called ORG. Below are the textbox properties of ORGID field.
> > > >
> > > > Attribute : ORGID
> > > > Lookup : ORG
> > > >
> > > > Here is the xml of the org lookup, I'm just trying to use the existing lookup.
> > > >
> > > > <table id="org" inputmode="readonly" selectmode="single">
> > > > <tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="org_lookup_tablebody">
> > > > <tablecol dataattribute="orgid" id="org_lookup_tablebody_col_0" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
> > > > <tablecol dataattribute="description" id="org_lookup_tablebody_col_1" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
> > > > </tablebody>
> > > > </table>
> > > >
> > > > Any idea on how to resolve the invalid binding error? or is there any other way to do it? Thank you all.
> > > >
> > >
> >
>