Tiffany_Hayden_
Collaborator
351 Views
6 min 46 sec read
Dieses Widget konnte nicht angezeigt werden.
Dieses Widget konnte nicht angezeigt werden.

Let's start at the very beginning. My journey into the Autodesk Community truly began when I needed to learn about drawing automation. I’d occasionally come across the forums before, but I hadn’t felt the need to dive in. That changed when I was assigned a project that demanded a steep learning curve and a quick turnaround—I suddenly found myself needing support. That’s when I began actively exploring Autodesk Community.

 

I quickly discovered that finding solutions often hinges on identifying the right keyword. For me, this meant diving into the API (Application Programming Interface) specific to Inventor and Vault, as my focus is on design and manufacturing. Thanks to my prior experience with other APIs, tracking down relevant keywords wasn’t as daunting as it might have been otherwise. However, I soon realized that drawing automation was a different world from model automation, bringing its own unique challenges.

 

Searching within an API can be hit or miss, but understanding the terminology you aim to automate makes finding those "magic" keywords much easier. My goal was to automate tasks like drawing document creation, sheet setups, views, dimensions, and more. Tackling these one small step at a time ("eating the elephant one bite at a time") became my approach.

 

Once I think I’ve pinpointed the right keyword, I head to the forums for further investigation. Sometimes the search yields answers, and other times it doesn’t—that’s the nature of it. When I do find relevant information, I focus on understanding how the method is applied. This often leads to questions about method inputs, especially when they involve unfamiliar data types, which happens frequently in API work.

 

In rare moments, you might strike gold and find exactly what you need on the first search—though infrequent, it does happen! When it does, you can tackle your task and move on. But sometimes, when more questions arise, you may need to ask on the forum yourself. I’ll admit that asking questions can feel daunting, especially knowing how many incredibly knowledgeable people are active there. Thoughts like, “What if the question already exists, and I just can’t find it? What if they think it’s a silly question? What if…?” might race through your mind.

 

Ignore those doubts—be brave! Ask the question. If you can’t find it, there’s a good chance others before you had the same question and never asked. By being the one to ask, you’re helping not only yourself but everyone who might follow.

How to Post:

 

Whether it’s your first post or your hundredth, the same principles apply. Here’s how to make your question clear and effective:

 

  1. Be Thorough: Provide as much information as possible about your problem. In developer forums, this often includes code. If you can, share the code that isn’t working—it gives others more to work with when helping you. If you’re unable to share specific code due to confidentiality, try creating a generic version by changing variable and method names, keeping the core functionality intact.

  2. Show What You’ve Tried: List the methods, approaches, or keywords you’ve already tested. This allows others to avoid repeating suggestions you’ve already explored and jump straight to alternative solutions.

  3. Be Kind, Courteous, and Engaged. Approach forum interactions with a learning mindset. It can be frustrating when solutions don’t come immediately, but remember, everyone helping you on the forum has full-time jobs too. Patience and understanding go a long way.

    • Be Engaging: After you post, keep track of responses. I recommend enabling notifications, but if that’s not for you, make a habit of checking back at least twice daily. When someone replies, acknowledge their help, and let them know if their advice worked or what new issues you might have encountered.
  4. Finish What You Started: If you find a solution, close the loop. Share the code or steps that ultimately fixed the issue, thank those who helped, and mark the correct solution as “Accepted.” This not only shows appreciation but also benefits others who may have the same problem by signaling a verified answer.

Is it a Bug?

 

Sometimes, the issue you’re facing might actually be a product bug. When that happens, there’s an additional step: head over to the Autodesk Community’s Idea Board. The Idea Board is designed for sharing ideas or bug reports for specific products, helping product teams track and prioritize issues.

 

When posting on the Idea Board, follow the same principles as with forum posts—provide thorough information and a link to your forum discussion. This link helps the product teams see the conversation that led to the conclusion that a bug may be at fault.

 

Leverage your network to get votes for your idea. If the issue affects your team’s efficiency, encourage colleagues and others in your community to vote. Each vote counts in showing Autodesk the impact of the bug or requested feature!

Am I Posting Too Much?

It’s easy to wonder, Am I posting too much without giving back by answering questions? Don’t worry—if you’re sharing questions and finding solutions, you’re already contributing to the community. Each resolved question helps someone in the future who might be facing the same issue.

 

Of course, if you have time to answer questions, dive in! Sharing your own code or insights can make a difference for others. But if, like me, you find yourself with more questions than answers and can’t respond as quickly as some of the super users, that’s perfectly fine. Keep asking, stay involved, and continue to engage. That’s what truly matters.


Feedback Community

If the products you work with have a specific feedback community, don’t miss out—get involved! The Feedback Community provides early access to upcoming releases, allowing you to test new features and provide input. For me, it’s a chance to explore the latest developments in Vault and Inventor and see if features I’ve requested over the years have been implemented. Watching an idea progress from a forum post to an implemented feature is immensely rewarding and reinforces that my input truly impacts the product’s evolution.

 

The Feedback Community also hosts regular webinars for Design and Manufacturing, called Inside the Factory (ITF). These sessions, led by product teams, offer a visual overview of what’s planned for the next update or major release, depending on the timing. Often, these webinars include a live mural board where you can share feedback and ask questions in real-time.

 

Inside the Factory is more than just webinars—it’s also an on-site event where you can connect face-to-face with the product teams, providing an opportunity to share feedback directly and build relationships within the community.

Is the Solution an AU Class?

Sometimes, you’ll solve a problem that’s not documented in the forums, isn’t a bug, and ends up sparking a creative solution. When that happens, consider proposing it as a class for Autodesk University (AU)—a great way to deepen your community involvement.

 

For instance, I once developed an approach to customizing Vault reporting. It was a feature that wasn’t well-documented and rarely discussed in the forums. After working through the challenges and creating an effective solution, I thought, If I struggled with this, others might too—why not share it?

 

Submitting a proposal for AU is never a guarantee of selection, but it’s worth taking the leap. Sharing knowledge is what motivates my active involvement in the Autodesk Community and AU, and presenting at AU is an incredible way to help others facing similar challenges.

A Special Thank You

I want to extend a heartfelt thank you to everyone on the forums who has shown patience and shared answers to my many drawing automation questions over the years. I am deeply grateful for this community—it’s given me more than I can express. Here, I’ve found not only a network of support but also true friends. Whether through the forums, idea boards, or speaker engagements, being part of this community has enriched me both personally and professionally. It’s a joy to keep learning and to grow in what I love doing every day.

Important Links:

Inventor Forums 

Vault Forums

Inventor Feedback Community

Inventor Idea Board

Vault Idea Board

 

Kommentare
Community Visitor
Community Visitor

Thank you for sharing your AutoDesk journey, Tiffany!  Yours is a path from looking for a solution to creating and sharing solutions yourself. Your passion for what you do with technology in general and AutoDesk tech in particular shows in how well-researched, tested, and laid out your posts are.  I've been following your writing for a while, but this is the first time I'm commenting.  Keep up the great work!

Explorer
Explorer

Thank you for sharing your journey, it's both inspiring and relatable.

 

The tips you shared are spot-on and will be handy for those getting started with the community.

 

Looking forward to seeing more of your contributions:daumen_hoch:

 

 

Community Visitor
Community Visitor

Great journey! I really appreciate how you’ve highlighted the value of asking questions and sharing solutions within the Autodesk Community. Your insights on using the Idea Board and participating in Inside the Factory are really helpful. I’m excited to engage more and contribute as well. Thanks for sharing your experience!

Collaborator
Collaborator