SPServices Cascading Dropdown not working

I've spent the better part of 2 day's trying to get the Cascading Drop downs to work. I was able to use the Country/Region/State example and implement and it worked perfectly. However, my lists would never work correctly. Here is an example of my data:

Every time I would run the code my SubSection drop down would correctly based on the Section Selection. However, my document type would never work. No error was thrown or anything. So after 2 days, I figured out that if there are multiple spaces in the text,
it would not work. I decided to put underscores "_" to see if that would work and surprisingly it did.

I'm not sure if this is a bug with the SPServices.CascadingDropdown or not, but wanted to pass along incase someone else was having the same issues as I was having.

It sounds like you weren't using the InternalName for relationshipListParentColumn or relationshipListChildColumn. If you had turned on debug mode, you should have gotten an error message. InternalNames have certain character, like spaces, encoded thusly:

Mark - I was actually using the Internal Name of the fields. The data represented above were the actual records. I purposefully made sure that my column names and list names did not contain any spaces.

I actually had the debug set to true. It would not error out when I had records with a bunch of spaces. I would go in, change one of the relationshipList fields to something that did not exist and it would return an error as expected. But as soon as I added
the underscores the cascade worked.

For example, one of the records had the following as a value that was to be populated into my 3rd cascading drop down:

It was a Data issue. The Columns were all set up correctly with no issues. Below are my calls and they all work now.

As I noted above, once I added the underscores to all of the data, it started functioning correctly. So the above now looks like "1.2.1__Request_for_Information_(RFI)/Sources_Sought/Pre-Solicitation_Conference(FAR_10.002)" with the underscores. It
now works as intended, but only once I added the underscores to the data.

Mark - Not sure what you've looked at, but I think the problem may have been a double space "1.1.1 Something goes here" in the data. I just replaced all my underscores back to spaces. Then I removed the double spaces between the WBS number and
the text. It appears to be working now.