I apologize if I came off short. Please never fear about making duplicate reports of issues - they help us to know how many customers are running into a given problem. Also, you may find a bug in a method that's different from someone else, which could change how we resolve that bug.
It's not a bad idea to try a quick search in the Forums before posting about a bug. And you can also take a look at the Release Notes for software - http://www.etcconnect.com/WorkArea/DownloadAsset.aspx?id=10737489083 is the v2.5.0 release note. There are sections for Issues Corrected and Known Issues Remaining. Even then, it's totally fine to say "I think the problem I'm seeing is related to xyz issue - here's what's happening for me - is that the same thing?"
I apologize if I came off short. Please never fear about making duplicate reports of issues - they help us to know how many customers are running into a given problem. Also, you may find a bug in a method that's different from someone else, which could change how we resolve that bug.
It's not a bad idea to try a quick search in the Forums before posting about a bug. And you can also take a look at the Release Notes for software - http://www.etcconnect.com/WorkArea/DownloadAsset.aspx?id=10737489083 is the v2.5.0 release note. There are sections for Issues Corrected and Known Issues Remaining. Even then, it's totally fine to say "I think the problem I'm seeing is related to xyz issue - here's what's happening for me - is that the same thing?"
don't worry, didn't get that wrong.
What you suggest is what I did before, but didn't find anything. That's why I asked, simply to avoid the exact same report.
