"There is no row at position 0." error message when changing the sort_order of a property

Hi Angela,

I haven’t tested to confirm, but I suspect that the issue is related to the fact that the source_id property data type is string rather than item. 

It’s ok to configure the labels, sort order, etc. for system properties, but I do not recommend changing how they fundamentally work (ex: deleting, renaming, changing data types). This can cause unexpected behavior and break core capabilities. 

Could you instead use a custom property like “fed_source_id” to manage the data in this use case?

Hi Eli,

for my use case the "item" datatype would work too. Choosing "string" as data type was just some precaution to avoid any connection that is not really there. But when I change data type to "item" I get the same error message.

This only affects my "fake" source_id property. I can´t even rename it, but luckily Innovator allows me to remove it.
If I use a new property "fed_source_id", everything works fine, so I go with this solution. Thanks for the fast help!

EDIT: I think I found the reason for this behavior!

Real "Source_id" properties typically come with an SQL index. But my fake property doesn't have any cause it wasn't created by Innovator in the context of a "real" relationship.
So the error is not thrown by updating the property itself (cause why should Innovator care for the sort_order?), but by Innovator trying to update the surrounding SQL elements, especially the Index. The error message itself wasn't thrown by Innovator, but by the SQL database that failed to do the update of not existing elements.

I once got the feedback that the forum is some kind of personal diary of my support questions. But people miss out that there are actual story lines that dis- and reappear. I already worked on the indexes a few month ago, I should have known better   Using additional custom indexes in SQL for custom ItemTypes - any best practice tips?