tracker issue : CF-3175667

select a category, or use search below
(searches all categories and all time range)

SerializeJSON() does not fully serialize array of entities from Entity Load

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Joel Watson / Joel Watson (existdissolve)

Created: 04/25/2012

Components: Language

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Public Beta / 285099

Priority/Frequency: Major / All users will encounter

Locale/System: English / Win All

Vote Count: 7

Duplicate ID:	CF-3145120

Related Bugs:
CF-3145120 - Similar to

Problem Description: When serializing result from EntityLoad(), array of entities are not fully represented in the JSON. Only the first two entities in the array are returned, while any additional objects in the array are represented simply as "{}". 

This is the same issue reported in for CF9.

Steps to Reproduce: Create two persistent entities, one for Art and one for Artists (using cfartgallery datasource). On Artists, create a one-to-many relationship with Art, using remotingfetch=true and fkcolumn=ArtistID

property name="arts" fieldtype="one-to-many" remotingfetch="true" cfc="art" fkcolumn="artistid";	

Actual Result: In the first result in the serialized json, the "arts" array has 5 elements. However, only the first 2 art entities are represented as expected, while the remaining 3 are represented as "{}". The same behavior occurs for other artist-art results.

Expected Result: All entities within the arts array should be populated with the correct structure and properties, just as if the result of EntityLoad("Artists") were dumped without serialization.

Any Workarounds: None that are known.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3175667


External Customer Info:
External Company:  
External Customer Name: existdissolve
External Customer Email:  
External Test Config: My Hardware and Environment details:



duplicate of bug #CF-3145120 (Comment added from ex-user id:vnigam)
Comment by Adobe D.
19651 | April 26, 2012 12:20:59 AM GMT
+1. Must be fixed. -- Adam
Vote by External U.
19652 | April 26, 2012 12:32:31 PM GMT
More and more developers are requiring JSON serialization to communicate with a variety of JS frameworks. Inattention to this bug only serves to prevent uptake of ORM in ColdFusion.
Vote by External U.
19653 | May 02, 2012 03:50:54 PM GMT
What's the status on this bug and why can't I find the duplicate one that's being referred as the actual open/closed bug??? CF-3145120
Vote by External U.
19654 | July 24, 2012 03:30:01 PM GMT
This is such a fundamental requirement for a contemporary 'web-centric' language, that a legitimate question is prompted here regarding whether it's possible to even bring Adobe CF to a project planning meeting anymore ... long-time CF lover here, but finding it more and more challenging to make the case for it within a management team ... come on Adobe, fix this issue ... it don't get more basic than this. I think Railo is about to graduate from the dev box!
Vote by External U.
19655 | December 01, 2012 12:49:18 PM GMT
Adobe - stuff like this may seem trivial, but as others have posted, it gets really hard to suggest CF as a platform when 1) the fundamentals don't work and 2) there is slow, if any response to fixing the problems.
Vote by External U.
19656 | January 15, 2013 03:54:43 PM GMT
CF10 was the worst update we have ever done. I think we started at CF4. Even updating to 6 from 5 was not bad. But, getting 10 live was a nightmare. I don't know how I can stay an advocate of CF if fundamental issues like this are left unresolved. You are leaving paying customers twisting in the wind. Do you have anything to say for yourself Adobe?
Vote by External U.
19657 | January 15, 2013 10:12:31 PM GMT
Please have this fixed. I hate writing getMemento() for everything.
Vote by External U.
19658 | February 04, 2013 12:50:53 PM GMT