PersonManage | Personnel management system | Object-Relational Mapping library

Btw, your JSON is invalid. You'll need to look at "Jonathan", see how the record has two UserName properties and no DisplayName. I assume the second occurrence should be named DisplayName.

The quick-and-easy solution is to use PreserveReferencesHandling, but this also needs to be used by the code that generates the JSON in the first place. If you have no control over the JSON being generated and you want to keep on using Json.NET (aka Newtonsoft.Json) then you'll need to define a separate DTO type (do not use class inheritance to avoid copying+pasting properties between your DTO type and your business/domain entity type, that's not what inheritance is for - if you're concerned about tedium then use T4 to generate partial types from a shared list of properties).

So add these classes:

I can see in the posted HTML code that some option group tags inserted incorrectly.

I suggest you refer to the example below that may help you to get the desire results in the IE browser.

You can try something like this:

Here's how I was able to make it work according to your rules. Please note it's a class method on Person model, not a manager method.

Try to add implicit parameter to the method

This code is correct. Your testing framework isn’t actually running the Mvc pipeline or invocation code and that, simply put, is the reason you’re not getting authorization errors.

It’s the same reason why you have to specify the action’s parameter and call the method yourself instead of providing a HttpRequestMessage object with the correct url.

You must change template code. Use below code:

I don't think its a good idea to change in migrations files. You can do the changes in model directly, and after changing the model, run ./manage.py makemigrations to generate new migration files.

Also, you need to subclass the model class from models.Model:

It's a bit of a quirk. Basically if you want to write custom methods in your QuerySet AND you want to be able to access them through Manager class you HAVE TO also implement them in the Manager class. Which doesn't look great as it's not very DRY for Django that tries to be as DRY as possible, hence the helper as_manager().

So, to answer your question these are not two different cases, but rather an example for a special case where you want to use your custom QuerySet methods through a custom Manager.