I'm thinking that all the entries in the return feed that do not have
g:id set refer to problematic entries. Are you iteration through the
result feed and checking the status of each entry? Also, to set your
own internal id (by which you reference your item in your system),
such that gb can recognize an update vs. an insert, you must set
entry.getGoogleBaseAttributes().addTextAttribute("id", your-id-here).
Use of the g:id aka entry.getId() value also identifies update
requests, but one cannot use setId() on a new entry; it's ignored/over-
written.
On Nov 3, 3:25 pm, JustRan <[EMAIL PROTECTED]> wrote:
> Hi there, we have finished the code to upload multiple items in one
> request with Google's API, but we got another problem when we are
> receiving response message.
> In the feedback object we received from google, the item which has
> errors has no <g:id> value send back, we need this value to insert
> into our LOG table to check which item has problems.
> Could you tell me how can we get the id back when the item has errors?
> Thanks a lot.
>
> PS: what we are doing now is recording the ids we uploaded and the ids
> we got with successful uploading, the differences between these two
> arrays are the ids have problems. But this is not a good way.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Base Data API" 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-Base-data-API?hl=en
-~----------~----~----~----~------~----~------~--~---
