Powershell data source instead of ps per form
closed
Bert Nieuwenampsen
We now have a few Powershell data sources, the largest being get-aduser and get-adgroup. I build everything around it, throubleshooting, logging, who can see what based on membership.
And now we have to do all this by every control in every form? I don't think that's the way you want to go.
There are many more places where you can make mistakes. If there is one thing that needs to be adjusted powershell technically, I have to go through all the forms. In addition, I must properly document where I use which statements.
This feels like going from central to decentral. I hope you will reconsider this !
M
Michiel van der Veeken
closed
Thank you for your feedback. We have taken this into consideration, but have decided not to change the current configuration setup regarding data sources and Dynamic forms in near future. Therefore I will close this feature request.
Bert Nieuwenampsen
Accessing an script via forms is useful and does work very nice
Tip: connect an existing data source to a new form item.
Just click om switch to editor.
Copy the right data config from another form.
From: "dataSourceConfig": {
Until the corresponding }
Always make a copy before playing with this ;)