Is this a proper use of Cascading Dropdowns?

Jan 22, 2010 at 6:43 PM
Edited Jan 25, 2010 at 2:38 PM

Marc,

Project: I am trying to streamline the functionality of an Administrative Assistant in Operations whose responsibility it is maintain the number of full-time employees at the company. To get this information, she currently sends a multi-page Excel workbook to the managers of 18 different departments. Each month, the managers must make their changes to the doc and send it back.

I've created one list with all relevant employees on it, along with their department, position, and time percentage (two decimal places between 0 and 1). The managers can now update information as it happens; the list is therefore always current, and the changes are written to an Audit list that the Admin. Asst. can use to make her Changes Report at the end of the month.

Problem: Most managers are responsible for Locations; and Positions are roles at that location. Three of the Departments, however, share resources among locations. In those cases, the manager is responsible for a role (described in the Location) column, and Position holds the main location or "home site" for that employee (e.g. "Location: Site 1, Position: Technologist" vs. "Location: Courier, Position: Site 1").

I'd like to use Cascading Dropdowns to limit the Positions list to "roles" for the Location-type departments, and "sites" for the Role-type departments.

Does that sound like this is the right tack to take?

Blessings,
Jim Bob

Coordinator
Jan 22, 2010 at 7:06 PM

Jim Bob:

Yes, this sounds workable.  SPCascadeDropdowns doesn't care *what* the data is, and duplication is OK if that's what you intend.  Let me know if you need help.  The first step is to set up the lists which contain the values and relationships. I'd use Site Columns for this on the root site if it is going to have utility anywhere else in the Site Collection.

M.

Jan 25, 2010 at 2:39 PM

(I updated the initial post to clarify the task a bit.)

I'm going try tackling this. You can be sure I'll ping you for help if (read: when) I get stuck. ;)

Blessings,
Jim Bob

Coordinator
Jan 25, 2010 at 3:30 PM

Bring it on!

M.

Jan 25, 2010 at 5:28 PM

OK. You asked for it... :)

Underline = site or site/subsite;
Italic = list;
Bold = column

  1. So, I have one list (Employees) of Operation/FullTime. Employees has the columns:
    • EffDate (Date and Time),
    • Employee (Single line of text),
    • FTE (Number),
    • Group (Choice),
    • Location (Choice),
    • Old Location (Single line of text),
    • Position (Choice),
    • Title (Single line of text),
    • Work Shift (Choice)
  2. A site column already exists (at root) named Department (Single line of text), that I think I can use for this.
  3. The other columns are Group and Position.

Here's what I think I should do:

  1. On Employees currently, I have Location as a choice column. I should:
    • change this to the site column Department.
  2. On Employees currently, I have Group as a choice column. I should:
    1. create a site-level list named Group, with columns:
      • Title (default; Single line of text), and
      • Department (Parent Drop Down List); and
    2. change out the Group column on Employees, to be a Child Drop Down List
  3. On Employees currently, I have Position as a choice column. I should:
    1. create a site-level list named Position, with columns:
      • Title (default; Single line of text), and
      • Group (Parent Drop Down List); and
    2. change out the Position column on Employees, to be a Child Drop Down List

Am I getting off on the right foot?

Blessings,
Jim Bob

Coordinator
Jan 25, 2010 at 8:33 PM

Jim Bob:

Sorry for the delayed response.  I think everything sounds right.  One thought: Might the Positions be reused?  Should there be another list which has the Title = the actual Position Title so that you can resuse them consistently?

M

Jan 26, 2010 at 3:44 PM

Marc,

OK, so rethinking what you're saying...

Each site column should be a Lookup into a List by the same name (ideally), right? So, I:

  1. Create a list (anywhere, right? but ideally where only certain people can maintain it) called Department which consists only of Title.
  2. Then, I create a site column called Department of type Lookup that points to the Title of Department list.
  3. Do the same thing with Group and Position.
  4. Then, I create the relation lists: Department Groups and Group Positions, as described in my previous post as Group and Position.

Is that what you're meaning by making the column for the Cascading Dropdowns as site columns?

Blessings,
Jim Bob

 

Coordinator
Jan 26, 2010 at 5:53 PM

You're reading me right again, Jim Bob.  IMHO, Site Columns (and Content Types) are one of the most powerful components of SharePoint, and one of the least used (at least properly).  By creating these columns as Site Columns, you start you develop a common taxonomy for the organization.  Things like Departments should be stored in exactly one place, and every other use of the Department concept should use that one source.

Since Lookup columns can only look up into lists in the current site, you should put the lists in the root of the Site Collection.  This also make the Site Columns available across the Site Collection as well. 

M.

Jan 26, 2010 at 5:56 PM

But wait...

If I create each of these as Site Columns, am I wrong to create the relationship lists with a Title? Should both columns be site columns (Department & Group; and Group & Position)? And if so, aren't they then Lookups, rather than Parent Drop Down Lists?

Am I messing this up?

Blessings,
Jim Bob

Coordinator
Jan 26, 2010 at 6:07 PM

The Site Column thing is really a discussion outside the SPCascadeDropdowns discussion.  For what you are outlining, you need the Location (Department), Group, and Position lists in order to indicate the hierarchy of relationships.  My point with the Site Columns is that, once you have those lists, you should use them for other things, and Site Columns let you expose that single version of the truth in other places.

M.

Jan 26, 2010 at 6:15 PM
Edited Jan 26, 2010 at 7:41 PM

Granted.

But, following your logic here, wouldn't they need to be set up like this:

  1. Department (list consisting of just a Title column)
  2. Department (site column; Lookup to Department; value=Title; name=Title)
  3. Group (list consisting of a Title column, and the Department site column)
  4. Group (site column; Lookup to Group; value=Title; name=Title)
  5. Position (list consisting of a Title column, and the Group site column)
  6. Position (site column; Lookup to Position; value=Title; name=Title)

Then, on Employee, are each of these Lookups, Parent Relationships, or Child Relationships? Or am I leaving out a layer?

Blessings,
Jim Bob

Coordinator
Jan 26, 2010 at 6:21 PM

Well laid out. On the Employee list, each of [Department, Group, Position] would be the Site Columns. (As we go through this, I have to keep re-second guessing myself!)  The columns themselves don't have the relationships; the relationships are enforced by use of the SPCascadeDropdowns function on the forms.

M.

Jan 26, 2010 at 6:41 PM
sympmarc wrote:

"The columns themselves don't have the relationships; the relationships are enforced by use of the SPCascadeDropdowns function on the forms."

Aha!!! There's the key I was looking for. Thanks for clarifying that.

More soon....

Blessings,
Jim Bob

Coordinator
Jan 26, 2010 at 6:43 PM
Edited Jan 26, 2010 at 8:54 PM

This is starting to sound like an EUSP article.  Or is it that everything these days sounds like an EUSP article to me?  Gotta be careful that Mark and Natasha don't get sick of me.

M.

Jan 26, 2010 at 6:45 PM

You and me both. I think they have two or three more of mine in the queue. ;)

...and this one's coming! :)

Blessings,
Jim Bob

Jan 27, 2010 at 4:23 PM

Marc,

OK. So I have done the above as follows:

  1. Created Location/Department list (static: LocDept) with column:
    1. Title (static: Title)
  2. Created Location/Department site column (type: Lookup; static: LocDept)
    1. Get information from: Location/Department
    2. In this column: Title
  3. Created Group list (static: Group) with columns:
    1. Title (static: Title)
    2. Location/Department (type: Lookup; static: LocDept)
  4. Created Group site column (type: Lookup; static: Group)
    1. Get information from: Group
    2. In this column: Title
  5. Created Position/Home Site list (static: GrpPos) with columns:
    1. Title (static: Title)
    2. Group (type: Lookup; static: Group)
  6. Created Position/Home Site site column (type: Lookup; static: PosHmSite)
    1. Get information from: Position/Home Site
    2. In this column: Title
  7. Added site columns to Employee list:
    1. Location/Department (static: LocDept)
    2. Group (static: Group)
    3. Position/Home Site (static: PosHmSite)

Added following code to CEWP on NewForm.aspx (I know, not your recommended practice. ;) ): 

<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.2.6/jquery.min.js" type="text/javascript"></script> 
<script src="/js/jquery.SPServices-0.4.8.min.js" type="text/javascript"></script> 
<script language="javascript" type="text/javascript">
	$(document).ready(function() {
		$().SPServices.SPCascadeDropdowns({
			relationshipList: "Group",
			relationshipListParentColumn: "LocDept",
			relationshipListChildColumn: "Title",
			relationshipListSortColumn: "Title",
			parentColumn: "Location/Department",
			childColumn: "Group",
			debug: true
		});
		$().SPServices.SPCascadeDropdowns({
			relationshipList: "GrpPos",
			relationshipListParentColumn: "Group",
			relationshipListChildColumn: "Title",
			relationshipListSortColumn: "Title",
			parentColumn: "Group",
			childColumn: "PosHmSite"
		});
	});
</script>

Getting the following debug error:

Error in function
SPServices.SPCascadeDropdowns
Parameter
parentColumn: Location/Department
Message
Column not found on page

I get the same error if I change parentColumn to "LocDept"

Thoughts? See any blatant errors?

Blessings,
Jim Bob

PS: Thanks, as always, for all of your help!

Coordinator
Jan 27, 2010 at 5:53 PM
Edited Jan 27, 2010 at 5:54 PM

It's not a good answer, but could you try taking the slash (/) out of the Location/Department column name in the Employee list and see if that helps?

M.

Jan 27, 2010 at 5:59 PM

Changed it to Location or Department. Still getting the debug error.

Also, I added relationshipWebURL: "/operations", to both calls (all three lookup lists live in http://site/operations/Lists; "Employees" list lives in http://site/operations/FTE/Lists).

Still no good...

Blessings,
Jim Bob

Coordinator
Jan 27, 2010 at 6:19 PM
Edited Jan 27, 2010 at 6:20 PM

I'm a little confused by the source you sent me.  Aren't the three columns you want to cascade: Location, Group, Position?  Let's just start with the first cascade:

$().SPServices.SPCascadeDropdowns({
  relationshipList: "Group",
  relationshipListParentColumn: "LocDept",
  relationshipListChildColumn: "Title",
  relationshipListSortColumn: "Title",
 
parentColumn: "Location",
  childColumn: "Group",
  debug: true
});

I'm not sure what you're doing with the Group, Location/Department, and Position/Home Site columns on the page.

M.

Jan 27, 2010 at 6:26 PM
Edited Jan 27, 2010 at 6:28 PM

Sorry... I have choice fields on the page with similar names. They have data so I don't want to delete them completely yet. I've renamed all of their Display Names to start with "DONT USE." But...

It's still telling me it can't find Location.

Coordinator
Jan 27, 2010 at 9:40 PM

NB: After an offline conversation (the telephone!) with Jim Bob and some noodling on this, we realized that the issue was that he was using jQuery 1.2.6.  Updating to 1.3.2 seemed to do the trick...

M.

Jan 30, 2010 at 8:14 PM

I seem to be having an issue very similar to Jim Bob's.  Noting your resolution, I attempted using 1.3.2 with the latest stable release as well as 1.4.1 with the 5.0 alpha release.  At this point, I've even attempted testing with a very simple list; here's the code:

<script language="javascript" type="text/javascript">
$(document).ready(function() {
$().SPServices.SPCascadeDropdowns({
relationshipList: "{C7B2231E-DA9C-4F7F-B5DB-822FF1FF85FD}",
relationshipListParentColumn: "Title",
relationshipListChildColumn: "Detail",
relationshipListSortColumn: "ID",
parentColumn: "Title",
childColumn: "Detail",
promptText: "Choose {0}...",
completefunc: null,
debug: true
});
	
});
</script>

 

This attempts to create a cascading dropdown for the simple list I mentioned; the list contains default values and one additional called 'Detail'.  The parent column is set to Title, and the child column is set to Detail.  I get an error much like Jim Bob's:

Error in function

SPServices.SPCascadeDropdowns

Parameter

parentColumn: Title

Message

Column not found on page

Coordinator
Jan 30, 2010 at 8:17 PM

The parentColumn should be the DisplayName of the column which is the parent for the "cascade" on the form.  It wouldn't be Title, as that is a Single line of text, not a dropdown.

M.

Jan 30, 2010 at 8:48 PM
Edited Jan 30, 2010 at 8:58 PM

Thanks for the quick response.  I corrected the error you mentioned, still working on the testlist.  Here's the code now:

 

<script language="javascript" type="text/javascript">
$(document).ready(function() {
$().SPServices.SPCascadeDropdowns({
relationshipList: "TestList",
relationshipListParentColumn: "General",
relationshipListChildColumn: "Detail",
relationshipListSortColumn: "ID",
parentColumn: "General",
childColumn: "Detail",
promptText: "Choose {0}...",
completefunc: null,
debug: true
});
	
});
</script>

This time, General is a 'Choice' field with 3 choices and Detail is a 'Choice' field with 3 choices.  Error:

Parameter:

parentColumn: General

Message

Column not found on page.

 

 

No idea what I'm missing this time.  Thanks again for your help, I'm a green sharepoint programmer who was just hired and throw to the wolves(weekend project before the first day of work, what gives).  Take it easy. =)

Coordinator
Jan 31, 2010 at 1:42 AM

Well, as the message indicates, either General isn't a column name on the page or General isn't a dropdown.

Maybe we should take a step back, and you could explain what you are trying to accomplish?

M.

Feb 1, 2010 at 3:16 PM
Edited Feb 1, 2010 at 3:31 PM

Marc,

Here's another issue I'm having: In my situation, where Location cascades to Group cascades to Position, I would like to let the user keep the same Group/Position if Location changes and the Group/Position combination is valid there, too. Currently that's working for Group, but not Position. I'll dig into that further, but if there's something glaringly obvious to you, please let me know.

Additionally, I would like to intercept a change that will cause the other values to no longer be valid, and give the user a message before completing the change. For example:

Record is set to Location = Clinic A; Group = Technical; Position = MRI Tech. If the employee transfers to Clinic B, but is still doing the same thing, I don't want Group/Position to change.

But, if I accidentally change the Location to "Business Office," there is no Technical Group there. Rather than blank out the Group and Position, I would like to alert the user that that Group and/or Position doesn't exist and have them verify the change before killing that data.

Thoughts?

Blessings,
Jim Bob

Coordinator
Feb 1, 2010 at 3:25 PM

Jim Bob:

Each change to the parentColumn is going to fully "redraw" the childColumn, so on the first point, you're out of luck unless you enhance the function.  I think that some of the things that you're trying to do here are getting pretty specific to your implementation.  You may be able to sort of "wrap" SPCascadeDropdowns to make it all work, but it may make more sense to customize SPCascadeDropdowns directly.  Of course that then branches the code, which might not be desirable.

M.

Feb 10, 2010 at 4:59 PM

Dear Marc,

Here's what I've done, but it's still not working the way I want:

<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js" type="text/javascript"></script>
<script src="/js/jquery.SPServices-0.4.8.min.js" type="text/javascript"></script> 
<script language="javascript" type="text/javascript">
	$(document).ready(function() {
		$().SPServices.SPCascadeDropdowns({
			relationshipWebURL: "/operations",
			relationshipList: "LocGroup",
			relationshipListParentColumn: "LocDept",
			relationshipListChildColumn: "Group12",
			relationshipListSortColumn: "Group12",
			parentColumn: "Location",
			childColumn: "Group"
		});
		$().SPServices.SPCascadeDropdowns({
			relationshipWebURL: "/operations",
			relationshipList: "FTE Group Positions",
			relationshipListParentColumn: "Group12",
			relationshipListChildColumn: "Positions",
			relationshipListSortColumn: "Positions",
			parentColumn: "Group",
			childColumn: "Position"
		});
		$("#FTE input[title=Location]").val("OPS");
	});
</script>

I've added id="FTE" to the main table within the DVWP so that I'm getting the right input field. On the screen, it shows that the Location is indeed OPS, and the other cascades work accordingly.

The problem is...
The value in the Location doesn't get saved on submit. All the others do, but not this one.

Since you've worked more extensively with the long lists associated with cascading dropdowns in SharePoint, I thought you might know how I need to set this up so that the value actually gets associated with the field, not just the input control that gets displayed.

Thanks!

Blessings,
Jim Bob

PS: Hope SF is profitable for you in lots of ways!!!

Coordinator
Feb 10, 2010 at 5:37 PM

I think you probably need to set the OPS value to be selected as well. So:

$("#FTE input[title=Location] option[value='OPS']").attr("selected", "selected");

I don't have this exactly right, but you probably see where I'm heading. I think that your Location column has 20+ options?

M.

Feb 10, 2010 at 5:40 PM

Cool. Yes, I had a feeling it was something like that...

Yes, it has 28.

I'll take the route and see if I can get it working right. Thanks!

Blessings,
Jim Bob

Coordinator
Feb 10, 2010 at 5:50 PM

As you know, with 20+ options, the control is a bit more complicated.  Let me know if you get stuck.

M.

Feb 10, 2010 at 5:56 PM
Edited Feb 10, 2010 at 6:01 PM

PS: The actual control looks like this: 

<span style="vertical-align:middle"><input name="ctl00$m$g_1eb65bd9_e3e4_4f52_9297_020e3b67b629$ff6_new$ctl00$ctl01" type="text"
id="ctl00_m_g_1eb65bd9_e3e4_4f52_9297_020e3b67b629_ff6_new_ctl00_ctl01" class="ms-lookuptypeintextbox" onfocusout="HandleLoseFocus()"
opt="_Select" title="Location" optHid="SPLocDept_Hidden" onkeypress="HandleChar()" onkeydown="HandleKey()" match="" choices="(None)|0|ACB|
2|ADC|23|AMR|4|ARC|3|CIC|5|Couriers|6|CP|7|ED|8|Float|25|GTN|9|IL|10|MID|11|MID INTV|12|MPT|13|MPT INTV|14|OPS|1|PRN|24|QRY|15|RCP|16|SCH|
17|SM|18|SW|19|Temp|27|Trainee|26|WIC|20|WLK|21|WMC|22"
onchange="HandleChange()" /><img alt="Display lookup values" onclick="ShowDropdown
('ctl00_m_g_1eb65bd9_e3e4_4f52_9297_020e3b67b629_ff6_new_ctl00_ctl01');"
src="/_layouts/images/dropdown.gif"
style="border-width:0px;vertical-align:middle;" /></span>

So, is option[value=''] really what I'm looking for?

Blessings,
Jim Bob

Feb 10, 2010 at 5:57 PM
Edited Feb 10, 2010 at 5:58 PM

Sorry for the dupe.

Coordinator
Feb 10, 2010 at 6:15 PM

I think this:

$("#FTE input[title=Location]").attr("value", "OPS");

M.

Feb 10, 2010 at 6:19 PM
Edited Feb 10, 2010 at 6:20 PM

That does update the input box right, but doesn't get the data into the record.

JB

PS: And wouldn't that do the same things as .val("OPS") ? Seems like there's another attribute or method I need to get to.

Coordinator
Feb 10, 2010 at 6:23 PM

This is a little hard to do from here. Try looking at the Location control in Firebug after you've set a value.  I'm almost positive that setting the "value" attribute should do it.  You might need to fire the change event on the associated select, too.

M.

Feb 15, 2010 at 4:02 PM

Dear Marc,

OK. Back to Monday morning grind...

So, on this NewForm page, I'm trying to set the default on the "top-level" (Location -> Group -> Position), setting Location to "OPS" (on this page; other pages will have other defaults).

Current jQuery code:

<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js" type="text/javascript"></script>
<script src="/js/jquery.SPServices-0.4.8.min.js" type="text/javascript"></script> 
<script language="javascript" type="text/javascript">
	$(document).ready(function() {
		$().SPServices.SPCascadeDropdowns({
			relationshipWebURL: "/operations",
			relationshipList: "LocGroup",
			relationshipListParentColumn: "LocDept",
			relationshipListChildColumn: "Group12",
			relationshipListSortColumn: "Group12",
			parentColumn: "Location",
			childColumn: "Group"
		});
		$().SPServices.SPCascadeDropdowns({
			relationshipWebURL: "/operations",
			relationshipList: "FTE Group Positions",
			relationshipListParentColumn: "Group12",
			relationshipListChildColumn: "Positions",
			relationshipListSortColumn: "Positions",
			parentColumn: "Group",
			childColumn: "Position"
		});
		$("#FTE select[title=Location]").val("OPS"); // for Firefox, which renders a select
		var locObj = $("#FTE input[title=Location]"); // for IE, which renders an input and an image if list is 20+
		locObj.attr("value","OPS");
	});
</script>

In Firefox, all is well. In IE, not so much…

IE Problem
The cascade works fine: the Location dropdown shows OPS and the Group is limited to the relevant groups for the OPS location. Choosing a Group cascades the Position list perfectly.

All looks well and the user clicks Save, which is when the problem shows up. The list being displayed is filtered on the OPS location and the new list item is not there. On further inspection, we find that the list item was saved, but with the Location is set to an empty string.

Thoughts

  • Is there a way to bind a different control that will render a select instead of the input/image combo, so that the jQuery for Firefox will work for IE?
  • Is there another way to set a default from the page level (rather than the column level)?
  • Is there a way to get the input/image combo to recognize the inserted value through triggering the HandleChange() event?

Anything else?

Blessings,
Jim Bob

Coordinator
Feb 15, 2010 at 4:08 PM

Jim Bob:

I promise to pay more attention to this today. ;+)

Have you tried this

locObj.trigger("propertychange");

after setting the value?

M.

 

Feb 15, 2010 at 4:20 PM

Marc,

Yes, I did. (Meant to include that in previous post.)

Also, I found this...

http://www.sharepointings.com/sharepoint-lookups-over-20-items-solution/

...which I tried and it didn't quite work either. I'm thinking it's because my lookup list is one site above this one. So, I added:

<WebPartPages:DataFormParameter Name="WebURL" DefaultValue="/operations/"/>

...inside <InsertParameters>, which didn't solve the problem.

Blessings,
Jim Bob

 

Coordinator
Feb 15, 2010 at 4:58 PM

No, you shouldn't need to do anything with the WebURL.  The jQuery library is going to identify the right list(s).

Triggering the click event on the dropdown image seems to work on my end.  (My testing construct is a little different.) Can you try it?

var locObj = $("#FTE input[title=Location]"); // for IE, which renders an input and an image if list is 20+
locObj.attr("value","OPS");
locObj.next("img").trigger("click");

M.

Feb 15, 2010 at 5:03 PM
Edited Feb 15, 2010 at 5:04 PM

Marc,

Cool.

That does the trick, though it leaves the dropdown displayed until the user clicks/tabs off. I'm fine leaving it like that, but if there was a way to make it close the list display, that would be great.

Blessings,
Jim Bob

Coordinator
Feb 15, 2010 at 5:24 PM

If you switch the focus to the Title column, that should take care of it:

var locObj = $("#FTE input[title=Location]"); // for IE, which renders an input and an image if list is 20+
locObj.attr("value","OPS");
locObj.next("img").trigger("click");
$("input[title=Title]").focus();

This feels a little sloppy, but it seems to work.

M.

Feb 15, 2010 at 5:40 PM

That takes care of insert, but creates a problem with update.

As I mentioned, I'm working with a DVWP so the same file draws the page four different ways:

  • normal list view (default);
  • insert view (just an entry form within the construction of the normal list layout);
  • edit view (looks like the normal view, but with an edit form displayed for the item being edited); and
  • remove view (similar to edit view, but with two "submit" buttons [Terminate and Resign] and the only editable field is for a required Effective Date)
    • Check your email for screenshots for clarity

Since they're all drawn by the same page (and therefore drawing the "same" controls), they all use the same jQuery calls to SPCascadeDropdowns. Now that the locObj.attr("img") is being "clicked" for the insert view, the Group and Position are being cleared out when it is "clicked" on the edit view.

Thoughts?

Blessings,
Jim Bob

Coordinator
Feb 15, 2010 at 5:46 PM

Does the FTE Id indicate the insert view? The click event ought to occur only for the image within that Id.

M.

Feb 15, 2010 at 6:16 PM

Actually, id="FTE" was on the table wrapping the whole webpart. (On other pages, there can be more than one so the ID was there to distinguish between them.)

So, I moved it down to the TRs that display the insert form and it still seems to work fine, but...

...the edit form is still clearing out the Group and Position.

Blessings,
Jim Bob

Coordinator
Feb 15, 2010 at 6:25 PM

I assume that "OPS" is a valid value for Location and that it has child Group and Position values?  Since you've got id="FTE" in position for the insert form, I don't think that any of the code below should touch the edit form.

var locObj = $("#FTE input[title=Location]"); // for IE, which renders an input and an image if list is 20+
locObj.attr("value","OPS");
locObj.next("img").trigger("click");
$("input[title=Title]").focus();

If I were local, I'd be tracing through the steps to see what's happening in the DOM at each point using the IE8 Developer Tools.

M.

Feb 15, 2010 at 6:40 PM

DOH!!! My bad... was testing on one that was created when things weren't working well. The Group on the item didn't exist for OPS Location.

I think I'm in business! (Of course, you'll hear about it if I'm not.) ;)

Thanks again for ALL of your help.

Blessings,
Jim Bob

Coordinator
Feb 15, 2010 at 6:42 PM

Whew! You bet!

M.