I've created a PowerShell script that serves as a search and filter tool for about 14 related datasets, which are currently in CSV format. The script can ingest these CSV files, build the necessary relationships between them, and let users query the data. The choice of PowerShell was based on necessity—it's the only programming language I can readily use right now. Some higher-ups have noticed the tool and want it to be available company-wide, but they want it to be more user-friendly, meaning they would prefer a GUI rather than command line access.
I'm looking for suggestions on what architectural options I can pursue to improve this script. I've thought about integrating it with Microsoft Teams for a chatbot interaction or SharePoint, but I'm unfamiliar with SharePoint development. While I could develop a Win32 app, I'd need the company to approve a code-signing certificate, which sounds like a hassle. Given all these constraints, what recommendations do you have to elevate my script to the next level?
5 Answers
It sounds like migrating your data to a database would be a great first step. Once the data is organized in a DB, it'll be much easier to design a user-friendly interface. Working directly with CSV files can complicate things, especially if data formats change frequently.
Absolutely! Setting up a database is definitely the right call.
If you're looking for a solution that many users can access, a web app is definitely the way to go. Deploying an EXE for multiple clients can lead to chaos with version control. Something like PowerShell Universal can help create a GUI for your script and manage user permissions effectively.
Consider using Power BI to visualize the data. While there is a learning curve, it can provide a user-friendly interface for data interaction. Plus, it integrates well with MS environments.
Good idea! I'll explore that option as well.
A web app could be your best route. Setting up a database backend with a web front end would allow for easy updates and scalability. If you're familiar with PowerShell, you can look into options like ScriptRunner or PowerShell Universal, which can turn your script into a web application and include an access management feature.
You could add a GUI to your PowerShell script using tools like PoshGUI or look into wrapping it in C#. Visual Studio 2022 is available for free, and developing a front-end with it can make your tool much more appealing. If the company needs a signed binary, just provide it and suggest they handle the certificate requirements.
Thanks for the resources! I'll check them out!
That makes sense! I haven’t done this because the data often comes in different formats. Standardizing the input is something I need to tackle.