Hey Jochen.

Thanks so much for the reply.  I had posted to the defect/issue/
ehnancement log as well and didn't see your note here until now.

I concur that both url's go to the same spreadsheet.

My problem due to the observed change is that I was storing the url as
a way to uniquely identify the spreadsheet.  Because of the change,
when i cycle through a user's spreadsheets I can no longer compare
based on the url, which I was using as a unique key of sorts.

1) did this infact change as I observed?

2) Is there a formula or api to equate one url to the other?

3) Is there another value I should have been using as a unique
identifier for the spreadsheet?

Again, my sincere thanks for any assistance you can provide.

Best,
Brian


On Oct 8, 2:45 pm, "Jochen Hartmann (Google)"
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> I will double check but I am not aware of this change. Both of the
> values that you see in the URI refer to the same resource.
>
> - J
>
> On Oct 8, 11:04 am, sobelito <[EMAIL PROTECTED]> wrote:
>
> > Over the past few days it appears the data populated in the
> > SpreadsheetEntry AlternateUri has been changed.
>
> > I used to see this 
> > format:http://spreadsheets.google.com/ccc?key=o02173698067007664392.30813658...
>
> > And now see 
> > this:http://spreadsheets.google.com/ccc?key=pCPHxDOCGKh5VObQI3zXDKg
>
> > Is anyone else seeing this?
>
> > My aplication used to store the AlternateUri as a reference ot the
> > document, and now that the SpreadsheetEntry.AlternateUri is populated
> > with a different value for the same spreadhseet, it has created quite
> > a problem for me...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Docs Data 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-Docs-Data-APIs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to