So, was it just that old API version we were using didn't support it and with the new API version it does? So we want to close this as no longer applicable? It doesn't seem to be a 5.6 issue which is where it is currently assigned.