v11/v10 iControl get_list change in behaviour? (/Common prefix)

Hi Samstep,

As you see there was a fundamental change in object keys, and part of the effect of that was to change what comes back from get_list and other methods that return names of (most) objects. (Other effects required us to deprecate a few entire interfaces because most keys that stil were not strings were made strings). We weighed the issue and tradeoffs and decided to make the query methods return the full name of the object including folder path. The new world includes folders, potentially with names that would look duplicate and cause havoc if you strip the path off, so we decided to make the new (and actual) name be the default, changing the behavior in a major release, 11.0, rather than making the default the stripped path and changing it later (what might look like: capriciously) down the road.

There is a workaround we put in to strip the path information if it caused people hardship but we decided not to make that the default for various reasons. The workaround you can try is the {set,get}_returned_path methods in System:Session. One interesting thing about that is the Session is persistent (by default on user id) so you can even run a separate request to set this and then run your normal code if you really needed to do it that way. Please be aware this is a workaround and is not intended as a general tool for stripping the path in ongoing new development; (most of) the objects have a path now and that's the new world to get used to. Also, there were a couple places in initial releases we missed respecting the ReturnedPath setting; those are fixed now. Sessions, by the way, are generally intended (in part) as a way to accomplish a given task with a bag of settings and still retain backwards compatibility for the most part; in particular they aren't persisted in anything but memory.

My apologies for the irritation you're experiencing -- I'd like to ask, what kind of processing are you doing on the name that has trouble tolerating the path? There are some scenarios that can show ill effect, like one might create a pool, then malfunction if one does not find exactly what one set on subsequent query; I'm curious as to what your code does.