Hi Marc,
Thanks for your quickly answer!
I'm using the following code:
It's strange that if I just go to my browser, Developer Tools and Console, the following utility has different behaviors when using FQDN and the site name:
$().SPServices.SPListNameFromUrl();
Thanks again!
Thanks for your quickly answer!
I'm using the following code:
$().SPServices.SPCascadeDropdowns({
relationshipList: "Product",
relationshipListParentColumn: "Group",
// listName: listName: $().SPServices.SPListNameFromUrl(),
relationshipListChildColumn: "Title",
parentColumn: "Group",
childColumn: "Product",
// debug: true
});
The custom page are in the current list context.It's strange that if I just go to my browser, Developer Tools and Console, the following utility has different behaviors when using FQDN and the site name:
$().SPServices.SPListNameFromUrl();
Thanks again!