New Post: SPCascadeDropdowns on a non-SharePoint Page

OK so I've got a new one to add to this...I have three drop downs now and three corresponding lists. I use SPFilter to fill the first "Parent" drop down. I'm guessing this is usually done automatically as part of creating the form, but outside the SharePoint UI, I have to populate it myself.

I then have two cascade functions to populate the two other drop downs - DD2 and DD3.

Everything seems to populate correctly, but I'm getting a server 500 (internal error) saying a list isn't found when it goes to do a search. If I drill down a little further in the SOAP packet, I see it's requesting a list that's got a blank name...where in the query would that be triggered? Is there some second-level request in cascade that I'm just not seeing. At a high level, this is what it looks like:

        $().SPServices.SPFilterDropdown({
            relationshipList : "Countries",
            relationshipListColumn : "Title",
            columnName : "Country",
            CAMLQuery: "<Eq><FieldRef Name='display'/><Value Type='Boolean'>1</Value></Eq>",
            completeFunc : null
        });
        //Automatic cascading dropdowns driven by **U_CollegeBU & **U_BURole lists.
        $().SPServices.SPCascadeDropdowns({
            relationshipList: "Regions",
            relationshipListParentColumn: "Country",
            relationshipListChildColumn: "Title",
            relationshipListSortColumn: "ID",
            parentColumn: "Country",
            childColumn: "Region",
            CAMLQuery: "<Eq><FieldRef Name='display' /><Value Type='Boolean'>1</Value></Eq>",
        });
        $().SPServices.SPCascadeDropdowns({
            relationshipList: "States",
            relationshipListParentColumn: "Region",
            relationshipListChildColumn: "Title",
            relationshipListSortColumn: "ID",
            parentColumn: "Region",
            childColumn: "State",
            CAMLQuery: "<Eq><FieldRef Name='display'/><Value Type='Boolean'>1</Value></Eq>",
        });

BTW - I see you depricated promptText - I get that it's not necessary on forms anymore due to the errors, but it's extremely helpful when working outside the SharePoint UI, so I definitely see a need to continue using it!