SPServices v0.7.1ALPHA8 Available for Testing

Yup, the alphas are coming fast and furious these days.

SPServicesI just posted a new alpha of SPServices v0.7.1. The most significant change in this alpha is the ability to have multiple child columns for a parent column in SPCascadeDropdowns. This was something I always intended it to do, but the last time I tried to work through it, probably well over a year ago, I wasn’t up to the challenge. This time I was, and I think that the function may also even be a teeny bit faster than it was in ALPHA7.

Here’s an example. In this simple list form, I’ve got a parent column called State and two child columns, one called City and the other called Second City.

By making two calls to SPCascadeDropdowns, both City and Second City are filtered based on the choice of State. I’ve also chosen to convert Second City from a “complex” dropdown to a “simple” dropdown by setting the simpleChild option to true.

$().SPServices.SPCascadeDropdowns({
  relationshipList: "Cities",
  relationshipListParentColumn: "State",
  relationshipListChildColumn: "Title",
  parentColumn: "State",
  childColumn: "City", // Child 1
  debug: true
});
$().SPServices.SPCascadeDropdowns({
  relationshipList: "Cities",
  relationshipListParentColumn: "State",
  relationshipListChildColumn: "Title",
  parentColumn: "State",
  childColumn: "Second City", // Child 2
  simpleChild: true,
  debug: true
});

Enjoy, and let me know if you have a chance to try it out.

3 Comments

  1. Marc,
    I’m confused on what the change realy is. Is it realy the support of multiple child cascading from the same parent? Or the change is to support cascading to multiple child columns from the same parent column, feom the same lookup List?

    I can tell you that I have been using the SPCascadeDropdowns function to populate multiple child columns from the same parent, but using different lookup lists.

    Parent column: Product

    Child column 1: Release – populated using the RELEASES table.

    Child column 2: Customer – populated from the CUSTOMERS table.

    Both use the Product field as the ‘Product’ as the relationshipListParentColumn.

    Paul

    Reply
    • Paul:

      It looks like the single parent / two children thing was NOT working in v0.6.2 and earlier. Then it DOES work in v0.7.0. I think I must have broken it in my work with v0.7.1, but now it’s fixed again in the latest alpha and more efficient.

      What I’m talking about here is simply one parent column for two different child columns. Whether or not the relationshipList is the same shouldn’t matter.

      It’s a long and winding road.

      M.

      Reply

Have a thought or opinion?