> If this **sectionNameKeyPath** is not the same as that specified by the **first sort descriptor** in fetchRequest, they **must** generate the **same relative orderings**. For example, the first sort descriptor in fetchRequest might specify the key for a persistent property; sectionNameKeyPath might specify a key for a transient property derived from the persistent property.

How can we give custom section names without having the “type” attribute

Thanx so much

Got it working!! Ended up returning nil for that method. Thanks for all the help. You can delete the previous post if you want. Sorry for posting it “anonymous”

AHA yes! Just searched that method and found it in “CoreDataTableViewController”. Now I just need to figure out how to remove this. This file is a template I found when going through core-data tutorials.

Hi Pyraego, you must have implemented – (NSArray *)sectionIndexTitlesForTableView:(UITableView *)tableView in your UITableViewDataSource?

Thanks in advanced!

I’m glad I could help Denis. I’m trying to jot down as many of these little gotchas as I encounter them.

Hi AD,

Fruit and Vegetables are values of the type property you’d create on the entity.

So with the RWFruit entity that I’ve got in my example, it has a type property and a name property. All the fruits have the type set to “Fruit” and all the vegetables have the the type set to “Vegetable”. Then you set the sectionKeyPath to “type” and it will group all the objects that have matching types.

Hope that helps explain it, I might upload an example project if it helps.

How do you set up the relationship between a manually created section header and a core data entity?

Thanks