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.
We have a custom application and the quick search function (the box with binocular icon on every application where you can type in the unique key of the object and the application will bring you straight to that record) is not working as expected. For the user to be able to use this function, they need to key in the unique identifier (similar to WORKORDERID) which is not visible to the user. If they search using the attribute that is visible to them (similar to WONUM) it will give them an error - No records found that match the specified query.
Action taken :
Modified the database. I've updated the attributeno of the field they need to use (like WONUM) from 5 to 1. Bounce the server and still I'm getting the same error.
Do I need to check any java codes? Thanks group.
That sounds like the problem you get when you accidentally delete the
primary index that the quick search uses for searching.
In the MAXATTRIBUTE table, pull up the data for your custom table and check
the PRIMARYKEYCOLSEQ column. The values in that column should match the
primary index you want to search for, i.e. with the WORKORDER table, you'll
find that the values in that column are the order of the keys in the
WORKORDER_NDX1 index.
I would suggest creating an index on the visible attribute, if you don't
have one already, and then setting the PRIMARYKEYCOLSEQ values accordingly.
Shannon
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
janice c
Sent: July-07-11 12:06 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Quick Search function (Binocular icon)
We have a custom application and the quick search function (the box with
binocular icon on every application where you can type in the unique key of
the object and the application will bring you straight to that record) is
not working as expected. For the user to be able to use this function, they
need to key in the unique identifier (similar to WORKORDERID) which is not
visible to the user. If they search using the attribute that is visible to
them (similar to WONUM) it will give them an error - No records found that
match the specified query.
Action taken :
Modified the database. I've updated the attributeno of the field they need
to use (like WONUM) from 5 to 1. Bounce the server and still I'm getting the
same error.
Do I need to check any java codes? Thanks group.
Thanks Shannon! Your a legend! Quick search is now working. :-)
--- In MAXIMO@yahoogroups.com, "Shannon Rotz" <shannonrotz@...> wrote:
>
> That sounds like the problem you get when you accidentally delete the
> primary index that the quick search uses for searching.
>
>
>
> In the MAXATTRIBUTE table, pull up the data for your custom table and check
> the PRIMARYKEYCOLSEQ column. The values in that column should match the
> primary index you want to search for, i.e. with the WORKORDER table, you'll
> find that the values in that column are the order of the keys in the
> WORKORDER_NDX1 index.
>
>
>
> I would suggest creating an index on the visible attribute, if you don't
> have one already, and then setting the PRIMARYKEYCOLSEQ values accordingly.
>
>
>
>
>
>
>
> Shannon
>
>
>
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
> janice c
> Sent: July-07-11 12:06 AM
> To: MAXIMO@yahoogroups.com
> Subject: [MAXIMO List] Quick Search function (Binocular icon)
>
>
>
>
>
> We have a custom application and the quick search function (the box with
> binocular icon on every application where you can type in the unique key of
> the object and the application will bring you straight to that record) is
> not working as expected. For the user to be able to use this function, they
> need to key in the unique identifier (similar to WORKORDERID) which is not
> visible to the user. If they search using the attribute that is visible to
> them (similar to WONUM) it will give them an error - No records found that
> match the specified query.
>
> Action taken :
> Modified the database. I've updated the attributeno of the field they need
> to use (like WONUM) from 5 to 1. Bounce the server and still I'm getting the
> same error.
>
> Do I need to check any java codes? Thanks group.
>
>
>
>
>
>
>
Hi guys,
I've successfully created the index and the quick search function works fine. However, after refreshing the index ( Go to Database Configuration > Select Action then Refresh Index), it wiped out the changes I've made in the PRIMARYKEYCOLSEQ. Below are the steps I've done.
1. Update maxattribute and maxattributecfg via SQL script
2. From Database Configuration application, I can see the PRIMARYKEYCOLSEQ of the attribute has been updated as per script.
3. Turn on admin mode then click REFRESH INDEX. Turn off Admin Mode
4. Log-off then log back on then go to Database Configuration. The changes I've made in the PRIMARYKEYCOLSEQ has been wiped out.
Did I miss any step that's causing this? Thanks everyone!
--- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@...> wrote:
>
> Thanks Shannon! Your a legend! Quick search is now working. :-)
>
> --- In MAXIMO@yahoogroups.com, "Shannon Rotz" <shannonrotz@> wrote:
> >
> > That sounds like the problem you get when you accidentally delete the
> > primary index that the quick search uses for searching.
> >
> >
> >
> > In the MAXATTRIBUTE table, pull up the data for your custom table and check
> > the PRIMARYKEYCOLSEQ column. The values in that column should match the
> > primary index you want to search for, i.e. with the WORKORDER table, you'll
> > find that the values in that column are the order of the keys in the
> > WORKORDER_NDX1 index.
> >
> >
> >
> > I would suggest creating an index on the visible attribute, if you don't
> > have one already, and then setting the PRIMARYKEYCOLSEQ values accordingly.
> >
> >
> >
> >
> >
> >
> >
> > Shannon
> >
> >
> >
> > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
> > janice c
> > Sent: July-07-11 12:06 AM
> > To: MAXIMO@yahoogroups.com
> > Subject: [MAXIMO List] Quick Search function (Binocular icon)
> >
> >
> >
> >
> >
> > We have a custom application and the quick search function (the box with
> > binocular icon on every application where you can type in the unique key of
> > the object and the application will bring you straight to that record) is
> > not working as expected. For the user to be able to use this function, they
> > need to key in the unique identifier (similar to WORKORDERID) which is not
> > visible to the user. If they search using the attribute that is visible to
> > them (similar to WONUM) it will give them an error - No records found that
> > match the specified query.
> >
> > Action taken :
> > Modified the database. I've updated the attributeno of the field they need
> > to use (like WONUM) from 5 to 1. Bounce the server and still I'm getting the
> > same error.
> >
> > Do I need to check any java codes? Thanks group.
> >
> >
> >
> >
> >
> >
> >
>
Hi,
I had the similar problem when I generated an additional index via DB
Config. I found out that maximo changes the primary keycolseq when the the
column sequence in the index is not the same than the column sequence in the
primary keycolseq. If you change the primary keycolseq then make sure that
you have an index exactly corresponding to the primary keycolseq. Maximo
checks this point whenever an index change for this object is made an if it
does not fit maximo will make changes.
Regards
Reiner
Von: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] Im Auftrag von
janice c
Gesendet: Montag, 29. August 2011 04:56
An: MAXIMO@yahoogroups.com
Betreff: [MAXIMO List] Re: Quick Search function (Binocular icon)
Hi guys,
I've successfully created the index and the quick search function works
fine. However, after refreshing the index ( Go to Database Configuration >
Select Action then Refresh Index), it wiped out the changes I've made in the
PRIMARYKEYCOLSEQ. Below are the steps I've done.
1. Update maxattribute and maxattributecfg via SQL script
2. From Database Configuration application, I can see the PRIMARYKEYCOLSEQ
of the attribute has been updated as per script.
3. Turn on admin mode then click REFRESH INDEX. Turn off Admin Mode
4. Log-off then log back on then go to Database Configuration. The changes
I've made in the PRIMARYKEYCOLSEQ has been wiped out.
Did I miss any step that's causing this? Thanks everyone!
--- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "janice c"
<carrillo_janice@...> wrote:
>
> Thanks Shannon! Your a legend! Quick search is now working. :-)
>
> --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "Shannon
Rotz" <shannonrotz@> wrote:
> >
> > That sounds like the problem you get when you accidentally delete the
> > primary index that the quick search uses for searching.
> >
> >
> >
> > In the MAXATTRIBUTE table, pull up the data for your custom table and
check
> > the PRIMARYKEYCOLSEQ column. The values in that column should match the
> > primary index you want to search for, i.e. with the WORKORDER table,
you'll
> > find that the values in that column are the order of the keys in the
> > WORKORDER_NDX1 index.
> >
> >
> >
> > I would suggest creating an index on the visible attribute, if you don't
> > have one already, and then setting the PRIMARYKEYCOLSEQ values
accordingly.
> >
> >
> >
> >
> >
> >
> >
> > Shannon
> >
> >
> >
> > From: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
[mailto:MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ] On Behalf
Of
> > janice c
> > Sent: July-07-11 12:06 AM
> > To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
> > Subject: [MAXIMO List] Quick Search function (Binocular icon)
> >
> >
> >
> >
> >
> > We have a custom application and the quick search function (the box with
> > binocular icon on every application where you can type in the unique key
of
> > the object and the application will bring you straight to that record)
is
> > not working as expected. For the user to be able to use this function,
they
> > need to key in the unique identifier (similar to WORKORDERID) which is
not
> > visible to the user. If they search using the attribute that is visible
to
> > them (similar to WONUM) it will give them an error - No records found
that
> > match the specified query.
> >
> > Action taken :
> > Modified the database. I've updated the attributeno of the field they
need
> > to use (like WONUM) from 5 to 1. Bounce the server and still I'm getting
the
> > same error.
> >
> > Do I need to check any java codes? Thanks group.
> >
> >
> >
> >
> >
> >
> >
>
Thanks for your help Reiner! I've updated the primarykeycolseq of all the attributes included in the new index (my bad as I've updated only the attribute that I need for the quick search function). I've added an extra step though which is to set CHANGED = 'Y' of the MAXSYSINDEXES and maxattributecfg object then apply configuration changes from front-end before refreshing index table. All the best!
Cheers
Janice
--- In MAXIMO@yahoogroups.com, "Reiner Voss" <Reiner.Voss@...> wrote:
>
> Hi,
>
>
>
> I had the similar problem when I generated an additional index via DB
> Config. I found out that maximo changes the primary keycolseq when the the
> column sequence in the index is not the same than the column sequence in the
> primary keycolseq. If you change the primary keycolseq then make sure that
> you have an index exactly corresponding to the primary keycolseq. Maximo
> checks this point whenever an index change for this object is made an if it
> does not fit maximo will make changes.
>
>
>
> Regards
>
>
>
> Reiner
>
>
>
> Von: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] Im Auftrag von
> janice c
> Gesendet: Montag, 29. August 2011 04:56
> An: MAXIMO@yahoogroups.com
> Betreff: [MAXIMO List] Re: Quick Search function (Binocular icon)
>
>
>
>
>
>
>
> Hi guys,
>
> I've successfully created the index and the quick search function works
> fine. However, after refreshing the index ( Go to Database Configuration >
> Select Action then Refresh Index), it wiped out the changes I've made in the
> PRIMARYKEYCOLSEQ. Below are the steps I've done.
>
> 1. Update maxattribute and maxattributecfg via SQL script
> 2. From Database Configuration application, I can see the PRIMARYKEYCOLSEQ
> of the attribute has been updated as per script.
> 3. Turn on admin mode then click REFRESH INDEX. Turn off Admin Mode
> 4. Log-off then log back on then go to Database Configuration. The changes
> I've made in the PRIMARYKEYCOLSEQ has been wiped out.
>
> Did I miss any step that's causing this? Thanks everyone!
>
> --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "janice c"
> <carrillo_janice@> wrote:
> >
> > Thanks Shannon! Your a legend! Quick search is now working. :-)
> >
> > --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "Shannon
> Rotz" <shannonrotz@> wrote:
> > >
> > > That sounds like the problem you get when you accidentally delete the
> > > primary index that the quick search uses for searching.
> > >
> > >
> > >
> > > In the MAXATTRIBUTE table, pull up the data for your custom table and
> check
> > > the PRIMARYKEYCOLSEQ column. The values in that column should match the
> > > primary index you want to search for, i.e. with the WORKORDER table,
> you'll
> > > find that the values in that column are the order of the keys in the
> > > WORKORDER_NDX1 index.
> > >
> > >
> > >
> > > I would suggest creating an index on the visible attribute, if you don't
> > > have one already, and then setting the PRIMARYKEYCOLSEQ values
> accordingly.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Shannon
> > >
> > >
> > >
> > > From: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
> [mailto:MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ] On Behalf
> Of
> > > janice c
> > > Sent: July-07-11 12:06 AM
> > > To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
> > > Subject: [MAXIMO List] Quick Search function (Binocular icon)
> > >
> > >
> > >
> > >
> > >
> > > We have a custom application and the quick search function (the box with
> > > binocular icon on every application where you can type in the unique key
> of
> > > the object and the application will bring you straight to that record)
> is
> > > not working as expected. For the user to be able to use this function,
> they
> > > need to key in the unique identifier (similar to WORKORDERID) which is
> not
> > > visible to the user. If they search using the attribute that is visible
> to
> > > them (similar to WONUM) it will give them an error - No records found
> that
> > > match the specified query.
> > >
> > > Action taken :
> > > Modified the database. I've updated the attributeno of the field they
> need
> > > to use (like WONUM) from 5 to 1. Bounce the server and still I'm getting
> the
> > > same error.
> > >
> > > Do I need to check any java codes? Thanks group.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>
>
>
>
>
>
>
Hi,
I think you need to amend maxattributecfg, as well as maxattribute,
otherwise it will wipe out your changes.
--- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@...> wrote:
>
>
>
> Hi guys,
>
> I've successfully created the index and the quick search function works fine. However, after refreshing the index ( Go to Database Configuration > Select Action then Refresh Index), it wiped out the changes I've made in the PRIMARYKEYCOLSEQ. Below are the steps I've done.
>
> 1. Update maxattribute and maxattributecfg via SQL script
> 2. From Database Configuration application, I can see the PRIMARYKEYCOLSEQ of the attribute has been updated as per script.
> 3. Turn on admin mode then click REFRESH INDEX. Turn off Admin Mode
> 4. Log-off then log back on then go to Database Configuration. The changes I've made in the PRIMARYKEYCOLSEQ has been wiped out.
>
> Did I miss any step that's causing this? Thanks everyone!
>
>
> --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> >
> > Thanks Shannon! Your a legend! Quick search is now working. :-)
> >
> > --- In MAXIMO@yahoogroups.com, "Shannon Rotz" <shannonrotz@> wrote:
> > >
> > > That sounds like the problem you get when you accidentally delete the
> > > primary index that the quick search uses for searching.
> > >
> > >
> > >
> > > In the MAXATTRIBUTE table, pull up the data for your custom table and check
> > > the PRIMARYKEYCOLSEQ column. The values in that column should match the
> > > primary index you want to search for, i.e. with the WORKORDER table, you'll
> > > find that the values in that column are the order of the keys in the
> > > WORKORDER_NDX1 index.
> > >
> > >
> > >
> > > I would suggest creating an index on the visible attribute, if you don't
> > > have one already, and then setting the PRIMARYKEYCOLSEQ values accordingly.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Shannon
> > >
> > >
> > >
> > > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
> > > janice c
> > > Sent: July-07-11 12:06 AM
> > > To: MAXIMO@yahoogroups.com
> > > Subject: [MAXIMO List] Quick Search function (Binocular icon)
> > >
> > >
> > >
> > >
> > >
> > > We have a custom application and the quick search function (the box with
> > > binocular icon on every application where you can type in the unique key of
> > > the object and the application will bring you straight to that record) is
> > > not working as expected. For the user to be able to use this function, they
> > > need to key in the unique identifier (similar to WORKORDERID) which is not
> > > visible to the user. If they search using the attribute that is visible to
> > > them (similar to WONUM) it will give them an error - No records found that
> > > match the specified query.
> > >
> > > Action taken :
> > > Modified the database. I've updated the attributeno of the field they need
> > > to use (like WONUM) from 5 to 1. Bounce the server and still I'm getting the
> > > same error.
> > >
> > > Do I need to check any java codes? Thanks group.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>