Maximo Wire - The IBM Maximo Help & Discussion Forum
February 10, 2012, 02:54:18 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Welcome to Maximo Wire, the IBM Maximo help forum. Feel free to register and ask any Maximo related questions you like.
 
  Home Help Search Login Register  
*
Pages: [1]   Go Down
  Print  
Author Topic: Invalid binding error on hiding a Textbox of More Search Fields  (Read 769 times)
0 Members and 1 Guest are viewing this topic.
NDROCKS
Newbie
*

Karma: 1
Posts: 15


View Profile
« on: August 30, 2010, 05:10:09 am »

Hi All,

I need your help. I have built a new application based on the original SR application. I have modified the attribute names (labels) wherever necessary. When I am using the More Search Fields dialog from the new application, I am facing a peculiar kind of error. I do not want the textbox for Classification (CLASSSTRUCTURE.HIERARCHYPATH attribute) from More Search Fields dialog. First I tried to delete the textbiox, then I tried hiding the textbox using Signature Options, tried hiding it using Security Groups. But still I am facing the same error which is as follows:
When I click on Advanced Search, the More Search Fields dialog window gives Invalid Binding error. If I press cancel button from the window, the dialog appears again with the fields and attributes I want in my application, but I cannot perform the search functionality.

If I keep the textbox as it is, this error doesn't come. But I do not want the textbox in my application. Please guide me on what to do.
Logged
NDROCKS
Newbie
*

Karma: 1
Posts: 15


View Profile
« Reply #1 on: August 30, 2010, 06:21:52 am »

Hi All,

I need your help. I have built a new application based on the original SR application. I have modified the attribute names (labels) wherever necessary. When I am using the More Search Fields dialog from the new application, I am facing a peculiar kind of error. I do not want the textbox for Classification (CLASSSTRUCTURE.HIERARCHYPATH attribute) from More Search Fields dialog. First I tried to delete the textbiox, then I tried hiding the textbox using Signature Options, tried hiding it using Security Groups. But still I am facing the same error which is as follows:
When I click on Advanced Search, the More Search Fields dialog window gives Invalid Binding error. If I press cancel button from the window, the dialog appears again with the fields and attributes I want in my application, but I cannot perform the search functionality.

If I keep the textbox as it is, this error doesn't come. But I do not want the textbox in my application. Please guide me on what to do.
Logged
NDROCKS
Newbie
*

Karma: 1
Posts: 15


View Profile
« Reply #2 on: August 30, 2010, 12:08:39 pm »

Hi All,

I found a workaround for this problem. However, m not sure whether MAXIMO experts would agree with me.

While trying to troubleshoot for the error, I had found that whenever I tried to change or delete the following control from the More Search Fields dialog in my application, I faced the said error.
<textbox dataattribute="CLASSSTRUCTURE.HIERARCHYPATH" hidelabel="true" id="qbe_grid2_1_1_grid5_24" inputmode="query"/>

I tried adding one Signature Option for that textbox in More Searcg Fields dialog, which didn't work. Then I tried hiding the attribute HIERARCHYPATH of CLASSSTRUCTURE object for my application in Security Groups for all users, which also didn't work out for me.

Then I added width="0" to the Application XML for that textbox in More Search Fields dialog box as follows:
<textbox dataattribute="CLASSSTRUCTURE.HIERARCHYPATH" hidelabel="true" id="qbe_grid2_1_1_grid5_24" inputmode="query" width="0"/>
I imported the XML back to the system and the error is resolved.
Logged
Ethen
Global Moderator
Sr. Member
*****

Karma: 16
Posts: 299



View Profile WWW
« Reply #3 on: August 30, 2010, 06:43:42 pm »

did you try deleting it from the xml.
Logged

regards,

Ethen...
NDROCKS
Newbie
*

Karma: 1
Posts: 15


View Profile
« Reply #4 on: August 31, 2010, 03:59:26 am »

yes Ethen,

I had tried deleting it from the XML also, but I had faced the same problem. So, i tried another approach and added width="0" in the XML itself as I had written in my reply before and issue was resolved.
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Recent

TinyPortal v1.0 beta 4 © Bloc
Powered by MySQL Powered by PHP Powered by SMF 1.1.15 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!