1) Create a new workspace
2) Upload the following participants loadfile (also attached):
entity:participant_id attr1 attr2
01 value01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21 value21
Note that the default page size in the UI is 20.
3) Now go to the data tab and view the participants. Note that only attr1 is shown, even if we go to the next page where participant 21 is (see screenshot). The attribute is still there, as FISSFC can verify:
timdef@wmc82-d41:~/src/fiss$ fissfc attr_get -p broad-firecloud-testing -w ui_bug -t participant
participant_id attr1 attr2
01 value01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21 value21
And even more confusingly, using the search bar returns participant21, apparently for no reason (second screenshot). It is probably worth it for the workspaces data model to maintain a set of all the attributes in it's back pocket (with an API endpoint as well) so it isn't dependent on scanning through the entire set of entities to find out which attributes exist.