I don't see a huge downside. Because if there is a strong leader with some good architecture knowledge, they should be able to cut down most of the downsides. However, there are a few limitations. For example, if you just leave the workflows to the developer, they may not properly document or organize the workflows. And then, if they're not organized, it's very difficult for another person to pick them up. Another downside is that two professionals can't work on one workflow at the same time. Let's say I have a huge workflow, and someone needs to support it. All I can do is virtually connect and share my screen, or I have to be with them together to look at the workflow and make updates. So the downsides are very few. But if you're more organized and have a dedicated architecture for your own solution, that will reduce a lot of downsides. But there are a few minor problems. For example, we can't browse multiple files. When we deploy a solution on a gallery, let's say I have ten different files, and I have to upload them all at once. This is something that's difficult in the gallery. So case by case, I see some downsides, but often we do something alternative. And then, recently, I came across one biggest downside. There's something called the Download Tool, which is used to push datasets over an API. If you have API credentials, you can configure them in this Download Tool. But I noticed that this Download Tool has a limited capacity. That means it can only push, like, X amount of values or X amount of strings, but it cannot push a huge amount of dataset. For that, I have to deal with the Python port again. So, that's a bigger downside, which I recently came across. In future releases, I would like to see Alteryx improve the connectors. Since Alteryx is a low-code platform and even our developers might not have extensive coding knowledge. If there's a possibility to enhance the connectors, it would be truly valuable. By connectors, I mean that I have come across some instances where these connectors incorporate a sort of programming language that could augment Alteryx's capabilities. This way, we could utilize these connectors instead of having to create a separate solution. For instance, if I intend to extract or transmit data from SFTP to Alteryx, it would be beneficial to have a pre-developed connector accessible within the community. Take the Power BI connector, for example. It's important for this connector to be consistently maintained. I'm aware that these types of connectors are already accessible within the community, but there are instances when they function as intended and times when they do not. Would it be possible to have a centralized repository where these connectors are regularly updated to align with the most recent versions? This would indeed be highly advantageous. I understand that it entails a significant amount of maintenance work. Nonetheless, given that Alteryx operates as a low-code platform and we frequently encounter a variety of challenges, we aim to minimize the need to engage additional resources such as Python or Java developers. Relying on such external dependencies can introduce complexities. Therefore, if Alteryx could introduce more connectors of this nature, it would be a substantial improvement. APIs and connectors play a pivotal role. In particular, we have numerous scenarios where I had to leverage APIs and SSEPs.
