# How To Programmatically Set A Course Advanced Fields

**URL:** <https://discuss.openedx.org/t/how-to-programmatically-set-a-course-advanced-fields/8901>\
**Category:** Development\
**Tags:** how-to\
**Created:** [December 11, 2022, 5:53am UTC](https://discuss.openedx.org/t/how-to-programmatically-set-a-course-advanced-fields/8901 "2022-12-11T05:53:27Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![arbrandes](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/arbrandes/32/158_2.png) [@arbrandes](https://discuss.openedx.org/u/arbrandes)\
**Post date:** [December 12, 2022, 2:35pm UTC](https://discuss.openedx.org/t/how-to-programmatically-set-a-course-advanced-fields/8901/5 "2022-12-12T14:35:32Z")

</div>

> [@sambapete](#):
>
> Unless I misunderstand what is going on, does that mean “Course Visibility in Catalog == None” no longer works under certain circumstances? If that is so, this is a problem that needs to be fixed and not toss under the rug.

Speaking for the BTR group (which owns the Nutmeg-targetted issue that I closed last week), our involvement hinges on:

1. The issue being properly identified, with instructions to reproduce it, and ideally (but not necessarily) for it to be part of the community test plan;
2. The issue has to affect the latest (and only) supported release: in literally half an hour, that is going to be Olive;
3. An assignee has to step up to manage the issue, which doesn’t mean they’ll have to fix it: they just chase after somebody to do it.

At this moment, as far as BTR is concerned none of the 3 are satisfied.

That doesn’t mean as a community we can’t fix the issue or draw attention to it. We can start by simply opening an issue to edx-platform with the reproduction instructions.

---

_[View the full topic](https://discuss.openedx.org/t/how-to-programmatically-set-a-course-advanced-fields/8901)._