The Fact Set is a useful Adaptive Card feature for presenting a tight list of keys and values: 
The Adaptive Card JSON for this list is very simple:
"type": "FactSet",
"facts": [
{
"title": "Date",
"value": "${Date}"
},
{
"title": "Open",
"value": "${Open}"
},
{
"title": "High",
"value": "${High}"
},
{
"title": "Low",
"value": "${Low}"
},
{
"title": "Close",
"value": "${Close}"
},
{
"title": "Volume",
"value": "${Volume}"
}
]
These fields are still bound by name, so it is just a matter of adding these fields to the field setup:
Creating a single card visual requires a little more thought than a multi-card visual, I have created a dummy table to anchor the card:
SingleCard = SELECTCOLUMNS(CALCULATETABLE(CryptoDetail,CryptoDetail[Symbol] = ""),"Symbol",[Symbol])
This dummy table then has a relationship, that I created to the detail table let's have a quick look at the data model:
The Single Card table provides a dummy Symbol for the Category, When we add the real Symbol it is added as 'First Symbol' from the CryptoDetail table.
The other test fields and the SparkLine are all 'Firsts'. For the numeric fields, I created a measure for each field, so that the unselected display would show the first field value, rather than the total:
Low = FIRSTNONBLANK(CryptoDetail[Low ],TRUE())
There are some assumptions here about blank fields, and I haven't done a default SparkLine.
This is the model as loaded into the sample PBIX file for the published Custom Visual, which we hope to get out there by Christmas. Meanwhile, this version of the Visual is available on the
Download Page