title: Power Platform Model-driven app Data Import with Alternate Keys
body: <p>I have a Data-driven app that exposes a List-view of an entity that has an alternate key attached to two fields.</p>
  <p>However, whenever I use the Import From CSV option, it ignores this alternate key and uploads duplicate rows without errors.</p>
  <p>Even setting up a specific duplicate detection rule for this entity doesn't prevent this row from being saved. (This might be because duplicate detection rules only throw warnings even when adding an item directly from the form).</p>
  <p>Additionally, setting a field to be required in the entity also didn't prevent a row from being added with no data for that field in Import from CSV, although I did discover that a Business Rule can solve this problem. However, I can't use a business rule to compare an incoming record against existing records; as far as I can tell, a business rule examines just the relationship between fields in the incoming record alone.</p>
  <p>Is there a way to tell the table/entity to maintain uniqueness across multiple fields and use this setting during Import from CSV?</p>
  <hr />
  <p>Also, bonus question, is there a way to lock the mapping schema for the import and prevent the user from being able to change it?</p>