Content Catalog Bug Report & Discussion

[Thommy_]

Today a new CC version was released: https://help.contentcatalog.autodesk.com/en/articles/9524719-content-catalo...

But it seem the bugs in the online version are still not fixed...

Atm there is no good place to post Content Catalog Bugs, the CC Forum is not activated yet, we are not allowed to post something like that in the beta forum. To start a discussion about all the bugs I make a start, because I don't like to open a Autodesk Support case for every bug...

Bug #1

After starting typing to add a new tag for a content item, the page is going blank and you need to refresh and load the page again.

Bug #2

Preview images of the content are sometimes not displayed e.g. filled regions

Bug #3 

Preview images of the content are blurry. Even if you add your own screenshots, the blurry image is added again as soon you edit the family

Bug #4

If I search through categories, the categories are displayed in English and German and the content is splitted between the two. For example if you look at the category "Sanitärobjekte", it just show a part of the available content, because the other part of the content is in "Plumbing Fixture"

Bug #5
To open the CC page you have to clear regularly the browsers site data including cookies. This needs also to be done to display the data correctly.

Bug #6

The App in Revit has only the US server ( https://contentcatalog.autodesk.com ) as tool and not the EU server ( https://contentcatalog.autodesk.eu )

Bug #7

3D preview of content items are not created & not displayed except OOTB content. Sometimes it happens that the own content is saved as an english version under the english named categories, and then the 3d preview is created.

Bug #8

If you edit an existing family with a type catalog in the family editor and upload it back to Content Catalog, the Type Catalog gets deleted. Even if you reupload the type catalog it is not displayed in the family as type catalog. The text file exists, but it is not assigned to to according family

Bug #9

Some fill patterns are sorted into the category "detail elements". So they are mixed with all the filled region types, which is super confusing. 

Bug #10

If you rename a family, it is not listed in the search results if you search via keyword of the new file name (at least for some time)

Bug #11

The website help.contentcatalog.autodesk.com has no https protocol

tbc...

[RSomppi]

You should let Autodesk know about these as this forum is not the right place. Autodesk barely moderates this forum. The product is new and bugs are to be expected. I'm sure they will be providing an appropriate place for your thoughts.

[Thommy_]

Autodesk CC Teams knows about this and their advice is to create a case for each bug. But the case system works not at all and it takes too much time. In addition I want to have an overview what other bugs are there, so I don't have to report them additionally. I need to know if CC is ready for deployment or if there are still bugs that need to be fixed before I get angry users. They make a secret about the development status, even if there are still unfixed critical bugs. So in my opinion Autodesk Forums are the right place. Otherwise I have to move this thread to RFO.

[RSomppi]

---

@Thommy_ wrote:

Otherwise I have to move this thread to RFO.

---

This.^^^

Bug reporting is not in the forum description.

---

@Thommy_ wrote:

In addition I want to have an overview what other bugs are there

---

Can't you keep your list someplace other than a support forum?

---

@Thommy_ wrote:

So in my opinion Autodesk Forums are the right place.

---

How many bug reports do you see here?

[RDAOU]

@Thommy_ 

Moin...By Beta Forum you mean the Content Catalog beta test or the Feedback Community Hub?  Autodesk Feedback Community 

It is more likely to get somone's attention on the latter

[Thommy_]

they don't like to see bug postings there any longer, because it is not beta any longer. Just if they have official beta test functionalities, you should post there 🙂 true story

[RDAOU]

Thats not for the beta only. There is a public feedback hub for current running versions which are still supported (ie: based on the date of this post anything between 2022 and 2025). There should be several tabs on the header, one for each test/preview program you are registered in and then a general feedback hub which is for public.

[Zachary_Juhl]

Currently having an issue where new revisions are not being made when uploading updated families. Only the original model is available for use despite everything being approved. 

[Ric_Weber]

@RDAOU, That link you provided for the Autodesk Feedback Community is for the beta testing and preview type forums...  There are no tabs to mention other than the one for Select a  project, which in my case lists the projects that I am part of.  

@Thommy_  is correct, the CC beta forum is only for new features and not for bug reports any longer since the service/app launched last year.  

So @Thommy_ should be placing support tickets through their manage.autodesk.com account page and select Content Catalog as the application that is not working.  

[RDAOU]

@Ric_Weber 

that's not my statement in the above image, that’s the Factory Team statement on the Feedback Community. 

products like Revit are open continuous project and any feedback or bug reported on the feedback community is logged and accounted if it falls writhing the development lifecycles of the project. The life cycle of the project not limited to the beta test period or prerelease tests nor does it end when the product version is released unless of course you believe that the update patched issued post release are solely driven by support ticket. 

Yes of course you can also submit a feedback via a support ticket but the process is not any different and could be in some cases longer and always lead to the same conclusion. An agent will contact you, tries to figures out what it is all about and the right subject matter focus group to forward it to. He/she will probably schedule a teams meeting or two also to understand how the bug you are reporting is affecting your operations followed by a couple of back and forth emails, then closes the case and tells you that it has been logged and forwarded to the dev team to look into it (which is not necessarily an in-house Autodesk team but could also be an external 3rd party like the case of content catalogue) 

 

[HVAC-Novice]

I don't know what that tool is supposed to do, but maybe they start by using a secure site??

[Ric_Weber]

@HVAC-Novice, Content Catalog is the Content Management System that Autodesk created (based on Unify, which they purchases) for users to be able to host their families to in the cloud and be able to insert them into projects.  Free for Autodesk Docs subscribers. As far as their help page goes, you are correct about that.  I have informed them of the fact that they still have links out there pointing to that old site.  I'm disappointed those are still there.  The new Content Catalog help page is: https://help.autodesk.com/view/CONTCAT/ENU/

@RDAOU, that does not say anything about reporting issues.  It only states that they are for feedback.  The items that @Thommy_ has listed are not feedback.  I do not have any of the issues that he is stating, therefore those are errors for him.  Lots of other firms are using CC and not seeing these issues.  I use it pretty extensively and have not seen these widespread issues.  

From the site: https://feedback.autodesk.com/project/home.html?cap=fda8e768-0b88-4e8a-9cf3-362b8351440c it specifically states: 

@Thommy_ If you don't want to issue support tickets, fine.  But if they don't have eyes on your specific scenarios, they can't fix them.  

[RDAOU]

@Ric_Weber

First, we need to establish whether you now acknowledge that your first statement was wrong. Then, we can move on to whether feedback includes reporting issues or not.

Alternatively, if you are such an expert, you could try helping to sort out the issue(s) others are having with CC rather than tagging others just to engage in a sterile discussion.