No the JSON response as interpreted by the store does not validate. Basically what's happening is it's ripping the first key off entirely.
Although, I performed a 2nd test as I showed yesterday and explicitly invoked the AJAX request and set JSON response to the value of a textarea and that response string did validate. This tells me that my .NET web service method is sending valid JSON and the problem is w/ the Designer/Store's interpretation.
I also just noticed something that looks kinda buggy.
When I hard code this valid response string into the data: config on my store and save. When i look at the actual file the quotes are missing around the first key but are present around all subsequent keys like so.
Guess what this doesn't validate on jsonlint.com.
Last edited by baushaug; 1 Mar 2012 at 7:01 AM.
Reason: corrected my response
Sorry I confused you there with the XML, JSON back and forth. The problem has been identified and here is what we've discovered.
After an hour and 20 minutes troubleshooting this with my manager, we have found out that the Sencha Designer 2 doesn't like rootProperty "d" that is specific to Microsoft.NET's web service JSON response. So this is a snippet of the actual string being returned from the web service:
It gives this error and for some reason removes the first key only starting with the value:
So we created a custom string without the proprietary Microsoft.NET "d" rootProperty and we were able to successfully "load data" to our store in Sencha Designer 2.
Hopefully this will help someone in the future and hopefully you guys can accommodate the .NET "d" rootProperty in future releases of the Sencha Designer 2.