Hi Andy, Thanks for the detailed report. I followed the steps and reproduced the issue on my test domain, I'm not aware of any recent changes that lead to this discrepancy, so I asked the engineering team to investigate. I'll get back to you as soon as I have any updates.
Claudio On Tue, May 31, 2011 at 11:12 PM, andy <[email protected]>wrote: > There is a problem with discrepancies between the resource ID shown in the > Google Apps UI and the resource ID used in the API. When creating and > interacting with resources via the API (as per: > http://code.google.com/googleapps/domain/calendar_resource/docs/1.0/calendar_resource_developers_guide_protocol.html), > then a resource ID needs to be provided. This can be supplied when creating > a resource and for interacting with an existing resource. > > A resource ID is also available in the Google Apps Resource UI. For > example, copied from the resource page in the control panel, exact IDs have > been changed for anonymity: > Email address > [email protected] > Use this email address to access this resource in calendar. > Resource identifier > 2439470685555 > Use this identifier to access this resource from the API. > > When obtaining a list of resources via the API, the returned resource IDs > do not match the ID in the UI. > > In the example above the resource ID shown in the UI is 243947068555, > whereas the ID used by the API is *testtesttest*. The XML fragment below > is data returned from the API (listing resources), and no trace of the > resource ID specified in the UI can be seen. Note that the email address is > the same (marked in green). > > <entry><id> > https://apps-apis.google.com/a/feeds/calendar/resource/2.0/domain.com/testtesttest</id><updated>2011-05-31T08:37:26.075Z</updated><link > rel='self' type='application/atom+xml' href=' > https://apps-apis.google.com/a/feeds/calendar/resource/2.0/domain.com/testtesttest'/><link > rel='edit' type='application/atom+xml' href=' > https://apps-apis.google.com/a/feeds/calendar/resource/2.0/domain.com/testtesttest'/><apps:property > name='resourceId' value='*testtesttest*'/><apps:property > name='resourceCommonName' value='test'/><apps:property name='resourceEmail' > value='*[email protected]*'/><apps:property > name='resourceDescription' value='test'/><apps:property name='resourceType' > value='test'/></entry> > > Because of this discrepancy it is not possible to use the resource ID as > specified in the UI to interact with existing resources as should be the > case. This presents a real problem when trying to update an existing > resource. It is not possible to use the email address in a consistent way > to identify a resource as the email address cannot be specified at resource > creation time. > > The resource ID in the UI did match the resource ID in the API in the past > and has broken recently. > > This problem has broken an existing application that was using this feature > and required admins to locate the correct resource ID and enter in the > application. There does not appear to be a workaround for this other than to > offer *another* tool to read the existing calendar resource IDs as the API > sees them. > > Is this issue known? What is the ID that is shown in the UI, it does not > match anything in the UI data? Can it be corrected? > > Thanks, > > Andrew > > -- > You received this message because you are subscribed to the Google Groups > "Google Apps Domain Information and Management 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-mgmt-apis?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Apps Domain Information and Management 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-mgmt-apis?hl=en.
