Just call it a ‘container object’ and you can be technically correct in almost every context.
See also: in SQL and Dataverse, a row is called a ‘record’, but in SharePoint and Lists, a row is called an ‘item’, and MAN do people get all pissy if you get them mixed up or refer to it as a ‘row’.
It’s even more aggravating when you understand that 1) they’re all different implementations of the ‘table’ data structure, so the term is still accurate; ‘records’ and ‘items’ are just subsets of ‘rows’, and 2) SharePoint and Lists are just SQL on the backend anyway.
Like, obviously you knew what I meant, but how is your ego gonna get stroked unless you preach about pedantic details that don’t matter?
Just call it a ‘container object’ and you can be technically correct in almost every context.
See also: in SQL and Dataverse, a row is called a ‘record’, but in SharePoint and Lists, a row is called an ‘item’, and MAN do people get all pissy if you get them mixed up or refer to it as a ‘row’.
It’s even more aggravating when you understand that 1) they’re all different implementations of the ‘table’ data structure, so the term is still accurate; ‘records’ and ‘items’ are just subsets of ‘rows’, and 2) SharePoint and Lists are just SQL on the backend anyway.
Like, obviously you knew what I meant, but how is your ego gonna get stroked unless you preach about pedantic details that don’t matter?