I'm running software (Software A) on our local server that has a number of contacts (ie, Name, Address, Phone, etc).
Using the API from 'Software A', I'm looking to retrieve these contacts (ie, Name, Address, Phone, etc) and POST these contacts in my Podio workspace via Podio API.
My question is: What Operations should my developer be using with Podio API? I'm thinking the "Get Contacts" operation?
Operations Screenshot
I ask because I noticed many of these operations under "Contacts" say "This operation is deprecated and will be removed soon."
Deprecated Alert Screenshot
No you don't want Contacts
That will retrieve your employees (the "members" that you pay-per-seat with your Podio subscription)
Contacts is becoming renamed as "Members" over time inside Podio, to make the distinction clearer.
The API you want to work with is "Items"
https://developers.podio.com/doc/items
This way you can edit and move data in and out from the "Podio App" you created for your Address Book storage (or perhaps you named this App as "Contacts", the label doesn't really matter)\
The "Address Book" app that you created will have an AppID which you can find by going to that app inside Podio, click the Wrench icon, then click Developer and you will see a field named: App ID for Address Book (or whatever your app is called)
This App ID is an 8 digit number, and you want to use the App ID to retrieve/edit unique Items (unique records, like for each person) from your Address Book app.
Related
If you type IAM <GO> in the terminal you'll be shown the UserID, UUID, CLID etc.
Is it possible to extract this information through blpapi when using the Desktop API to connect via BBComm? I've seen references to Identity and populating that by sending an AuthorizationRequest but it appears that's only relevant for SAPI/B-PIPE.
To the best of my knowledge and after asking a couple of Bloomberg reps - this isn't possible. The best work around which I've found is: each user creates an EQS screen called their UUID. Add some filtering which causes this screening to return nothing. Then the application, upon start up, requests all possible UUIDs as EQS screens and stops when it doesn't get back an error - that's the UUID.
This is a dirty, dirty hack and, granted, this only works if you have few distinct users using your system. You don't want to ask may users to create such a screen and probably don't want to iterate over thousands of EQS screen names.
There is a "SID report" which is provide together with monthly invoices from Bloomberg which contains the UUIDs for users - this can be used to look up existing users but when setting up a brand new account you have to manually copy this information out of the terminal.
I need to use themoviedb.org for one of the apps I am working on. For using the API, I need an API key. How do I get an API key on themoviedb.org?
I found this in the forum:
You can request an API key by clicking on the "API" link from within your account page on the left hand sidebar. See here
In terms of making things faster for people, the URL for application is here these days (Under Account>Settings>API as previously mentioned): https://www.themoviedb.org/settings/api
You'll want to start with a Developer key as wait time for a Developer key is zero (immediate). A commercial key, as far as I understand it, is only appropriate once the app is developed and running. Turnaround for a commercial API key is about 3 days-ish though obviously could vary.
Once you have a key, inside the doco pages there's a "Try It Out" tab which lets you do calls. The normal code flow (for getting movie details) would be something like:
Get Configuration (needed for image paths, should be cached)
Search Movies (returns a list, find the numeric id for the one you want in the list returned). Be aware there might be duplicates returned - you can use the year of release, title and language to find the one you want.
Get Movie Details with the movie numeric ID, with "append_to_response" of "credits,images,trailers" so that actors, writers, directors, and trailers (aka videos) are returned.
Check doco for how to find the actual image paths, using configuration values fetched above. It's generally considered courteous to copy the images you want to use to your own server rather than serving them from TMDB's server.
The single / multiple contact pickers don't seem to have any way of specifying a title, so the user is suddenly just confronted with the big list of contacts from the people hub.
We can, of course, tell the user in advance but that adds in a level of design limitation (launching from an app bar button for example).
Am I missing the API for this as well or is this currently an unsupported scenario?
I want to access the iPhone "Favorites" numbers (the ones that can be found in the "Phone" application). I've searched among the properties specific to each contact from the Address Book and I even had a look at the Address Book database, but I couldn't identify which property or field from the database indicates which are the favorite numbers.
Since "Phone" is an application installed by Apple on the iPhone I was expecting to find such a property in the database. However, I think that it might be possible that this application stores the favorite numbers independently of the Address Book database.
Has anyone encountered this problem before and if yes, could you please clarify this matter for me?
I don't think this is possible. I would expect the "Phone" application itself stores the most used numbers without exposing this infomation to other applications.
This question is a duplicate of Find Favorite contacts from the iOS Address Book API
It's currently not possible to access favorite contacts via a public, app-store legal API.
What’s considered ‘best practice’ when saving Address Book contacts in Core Data?
I’m writing an iPhone App, based on Core Data, where I need to save and recall Address Book contacts as part of the data model.
In the UI I plan to present a screen where the user can pick a contact from the current Address Book, create a new contact to store in the Address Book, or just create a ‘one-off’ contact with no saved record, local to the App only. These contacts are tracked in the context of the orders they have made, and not all contacts will require saving outside the App itself.
It feels ‘wrong’ to copy the data from the Address Book if using an existing entry, but not sure what to do if an Address Book record is edited or deleted.
I only need to track name and photo for the purposes of the App, so gut-reaction is to store the ABRecordID, and—because these can apparently change(!)—the first and last name, and only update local record if it’s updated (how to track that?).
Or can you store a ABRecordRef directly? (I imagine they aren’t persistent?)
I’ve done some searching on Google, and here, but can’t find any code samples or discussion on the integration of Core Data and Address Book in this manner; just lots of stuff on each in isolation.
Any one with some experience/gotchas on this subject point them out, or point me in the direction of some more reading?
Thanks.
Andy W
I would store the ABRecordID and then handle the situation for when they change although I have not personally seen a case where they change except when the user deletes all data and restores it from another source (moving from MobileMe to Google for example).
See Apples online Documentation on how to handle changing ids and what to store.