Hi,

Sorry for the inconvenience caused. The field escaping is back again
as we have temporarily held back on an update on Google Apps
Reporting.
The escaping will be removed from the field as we plan to push the
update again which has a lot end user benefits in terms of performance
and data consistency.  An announcement will be made here once that
happens.

Once again, we apologize for the trouble you may have gone through.

-Anirudh



On Feb 5, 8:14 pm, "[email protected]" <[email protected]>
wrote:
> The reason behind this is I am trying to insert the retrived report
> into a database. For consistency, please do not escape any strings out
> of the blue.
>
> On Feb 5, 1:44 pm, "[email protected]" <[email protected]>
> wrote:
>
 Hi,
>
> > I am just wondering why the suspension_reason field is being escaped
> > again? What is the reason for the change this time?
>
> > On Jan 29, 12:29 pm, "Anirudh (Google)" <[email protected]> wrote:
>
> > > Hi,
>
> > > The behavior of reporting hasn't changed. We changed the content of
> > > the suspension_reason field so that it doesn't need to be escaped
> > > anymore.
> > > We definitely appreciate your feedback and will do our best to
> > > communicate more effectively in the future.
>
> > > -Anirudh
>
> > > On Jan 28, 9:49 pm, "[email protected]" <[email protected]>
> > > wrote:
>
> > > > i realized that the data of the "suspension_reason" field in the
> > > > accounts report has been changed from a double quoted string to just a
> > > > string, why hasn't the update been communicated?- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Apps APIs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/google-apps-apis?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to