Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help needed with a picklist #2307

Closed
davesmits opened this issue Aug 22, 2016 · 3 comments
Closed

Help needed with a picklist #2307

davesmits opened this issue Aug 22, 2016 · 3 comments
Assignees

Comments

@davesmits
Copy link

I am writing a task to automatically submit an app to an MDM envoriment. I have everything in basic working but I now have to fill in an App Id myself. I try to make this a picklist in the UI.

For me it's not really clear how the picklist is working and seeing two different approaches using dataBindingSource and sourceDefinitions.

The webservice to get this data is AAD protected. So I have a clientId, ClientSecret and TenantID. In my powershell script I use these variables to get the access token. these values above are stored in a connected account.

During the build the powershell script reads the values out the connectedAccount to get the access token and then performs the right calls.

How I do this for the picklists? someone that can help me in the right direction?

@bryanmacfarlane
Copy link
Contributor

RM added the picklists. Sriram can point you to documentation.

@GitHubSriramB
Copy link
Contributor

dataSourceBindings is what we would recommend to use going forward for dropdown scenarios. sourceDefinitions are still supported but mainly from a backward compatibility perspective. We will not be doing any feature enhancements on top of sourceDefinitions.

We are in the process of documenting how to create custom endpoints. We will include details around dataSourceBindings in that.

In this thread, I mentioned how dataSourceBinding/dataSource work together:
#973

We currently do not support generating access token using the other details in the endpoint & use it in subsequent query to populate drop-down. Is it possible to pre-create an access token and provide it as part of the endpoint? If so, we should be able to use this pre-created token to query dataSources and populate drop-downs.

@davesmits
Copy link
Author

Thanks. Generated tokens are valid for 12 hour so not going to work for me. Thanks will keep close watch if its going be solved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants