@lvalics I agree, as long as itās not spammy and the post is genuinely helpful, I think it should be allowed. The issue is when people go overboard and flood threads with overly long or off-topic AI content, making it harder for others to find the actual fix. A balance is definitely needed in this AI-driven era.
@rbreen @bartv Thatās great insight, Iāve heard good things about Tableau. Your experience would definitely be valuable here. That said, we need to make sure weāre not unintentionally limiting or discouraging contributors. It can be disheartening when people like myself put in time to solve issues, only for the original poster to mark something else, or nothing at all, as the solution.
Iāve worked in tech support for years and even monitored and reported stats for TSEs. Thereās nothing more frustrating than being discredited for the exact solution you provided, especially when it gets overlooked or reassigned. In this forum, anyone can work on any thread, so the least that could be done is reviewing and assigning the solution to the rightful responder, especially now that thereās a competitive element involved.
That lack of recognition creates a frustrating environment. Personally, Iāve slowed down my contributions compared to the previous month, partly due to this and a few personal reasons, but I should be back in full swing soon.
At the end of the day, it just depends on what level of support you want to build within the community. If you want to keep good contributors active and engaged, the system has to be fair. Otherwise, itās easy to lose people and hard to get that quality support back.
Itās 2025, and adaptation is key. New innovations create success, but only if the support system evolves with them.
Implementing a flag feature for threads that are clearly solved but left unresolved could really help. It would make it easier for others to find relevant answers quickly, and also help tidy up the community by letting active users submit those threads for review and proper attribution.