I am Customizing the Azure APIM Developer portal. For the Non Production enviornment like Dev, QA etc I am using the same instance of APIM. But the API name is different. I would like to either group them by name so that I see all the API's related to Dev First and rest of the enviornments later. Is there a way i can achieve it? Also we have one template called API List which we can customize. Can we create multiple pages from this template so that I can create different versions of API List for each enviornment?
Your best bet is to use tags. You can assign them to APIs and group by Tags in APIs list. Look for this button next to search field:
if you don't have one, check your customized template, and compare it to default one.
Related
I have created a Shopify Store which needs to contact another outside web service to send a query and then build the products based on the query response data.
Is it possible to do with Shopify?
If yes, then how should I go about implementing it?
I have tried looking into the docs but it seems like the only option is to connect with Admin API to add products. However, I don't want to store product data but instead rely on the API.
You do want to use Admin API calls. The reason is simple. They let you create products in Shopify, in bulk. Why fight the power! Using the Admin API has nothing to do with storing products, not sure why you're afraid.
So you get your product info from wherever, format it into Shopify-compatible data, inform Shopify of your data, and sit back and relax. The bulk building is really quite simple for a pattern. You can also build yourself a CSV to import where you also format the data to be compatible with Shopify. So there are two options for you right there.
I have a requirement to expose the APIM Developer Portal to external partners, I want the developer portal to be my one stop shop for these partners to access and learn everything they need to know about my APIs, in the main APIM Developer Portal satisfies that requirement but when I want to add new content e.g. specific design, architecture, user guide documentation etc about the API it starts to get very confusing, for a start it looks like the depreciated publisher portal (which still exists) is the only place that I can add new pages. The new pages seem very limited and clunky and cannot be amended in the new version of the portal. There is also very limited documentation outside the standard MS stuff and nearky all of that relates to amending the current pages and templates.
My site will go live at the end of the year and I don't want to find one day these new content pages missing from the portal and my supporting documentation removed.
Does anybody know where Microsoft is going with the developer portal for customizing outside outside the standard templates they offer or can anybody supply me with a link of documentation that addresses new content pages?
It looks like the depreciated publisher portal (which still exists) is the only place that I can add new pages
Yes, you need to use the publisher portal to add new pages.
The new pages seem very limited and clunky and cannot be amended in
the new version of the portal.
What do you mean by new version of the portal?
I am going live at the end of the year and I don't want to find one day these new content pages missing from the portal and my supporting documentation removed.
If your worry is that API Management will automatically remove your content because of publisher portal deprecation - you can rest assured this is not going to happen, especially without any previous notice.
Does anybody know where Microsoft is going with the developer portal for customizing outside the standard templates they offer?
There is some work planned to refresh the developer portal. Can you please elaborate more on what you are trying to achieve? What is your goal?
One can edit those pages in 2 places: Publisher Portal and Developer Portal.
In the Publisher portal you can add widgets to predefined areas on the page. For example you can add a HTML widget to the home page for authenticated and non-authenticated users. Rasmas Gude has a great article about that here.
In the Developer Portal you can change the information shown on each page by editing the template. There's a edit template icon available on the left for administrator. If you click that and then select the section you want to edit a split screen will appear below. The left have is DotLiquid markup and the right is the data model for that section. With that information you should be able to modify the page in the manner you wish.
If they are decommissioning the publisher portal, it will be enabled in the azure portal. Earlier we have the API, Products and users etc in the publisher portal. that are added in the other portal. The deprecation of the portal, dosnt mean the existing functionality will fail, which have the alternatives.
I am working to develop an external application that will be used to update items in a Podio workspace via AJAX request. However, I'm having a bit of a hard time understanding how to properly generate an API key...
In the API key generator, it asks for the 'Application name (displayed in stream byline)' - what exactly is meant by this? Is 'Application' just an individual app in our workspace? If so, is it possible to generate one API key for the entire workspace? We will need to update items inside of many different apps (including apps that do not yet exist) from the same external application, and would probably prefer to not have to generate a unique key... it would be preferable for us to just have one API key with which we can update items in all of the apps in our workspace.
Application name is not Podio individual app in your workspace, but rather name of application that you develop. So, in sentence:
We will need to update items inside of many different apps (including
apps that do not yet exist) from the same external application ...
Apps - means Podio applications
External application - means application that you develop and you want to generate your API key for it, so it would be natural to name your API key in a way that you know which application is using it.
I've created a couple of dashboards in my rally environment and since I cannot make them project viewable I would like to share the dashboard without sharing it with the entire workspace.
Is this possible? If so how?
Unfortunately, shared pages in Rally get shared with everyone and cannot be set to be visible at the project level. You will need to share with the desired users which apps and settings (or code if it is a custom HTML app) you are using in order for them to be able to re-create these themselves.
You could always post this as an idea at https://ideas.rallydev.com to get visibility for the functionality you are looking for.
Hi
I am currently working on an application which is implementing salesforce.com REST api. I have done all the authentication part and received all the info needed. Now I want my application to push the leads into the customer's account. But the lead fields can be customized and different customer use their different custom fields, so any1 can suggest me how to add that custom field in my form which will be pushed to the customer's salesforce account.
Thanks
You can use the describe resource in the REST API to obtain the metadata about the Load object, including all the fields.
https://{someinstance}.salesforce.com/services/data/v20.0/sobjects/lead/describe
You can use the list of fields to drive your form, and to control what you subsequently POST to /services/data/v20.0/sobjects/lead to create the new lead.
Here's the link to the REST API pilot docs incase you haven't seen them
No idea if the REST API supports describe() calls, they're a way of querying for all metadata about table (columns, their types etc). In normal webservice API this info can be found at http://www.salesforce.com/us/developer/docs/api/index_Left.htm#StartTopic=Content/sforce_api_calls_describesobject.htm#topic-title
the Metadata REST API was put on hold by Salesforce, so there is no REST API for Metadata (there is some limited support in the Tooling REST API, but not enough to create an object).
https://salesforce.stackexchange.com/questions/20763/creating-a-custom-object-using-rest-api