creating Mongo fixed collection but still having shardKey in payload

While creating fixed collection (Unsharded 20GB limit) in both MongoDB v3.6, v4.0 accounts, request payload still includes ShardKey even through the input box is hidden already.
This behavior leads users always creating partitioned collection no matter which sharding option they opt-in.
Request payload should remove "shardKey" property, thus allows Portal-Data Explorer creating fixed collection in specified database.


Start at the Data Explorer's MongoDB collection-creation flow and reproduce the fixed-collection request for the MongoDB v3.6 and v4.0 accounts described in the issue. Confirm that the payload omits the shardKey property when the sharding option is disabled, and verify that a fixed collection is created in the specified database.

Written by the indexing model from the issue text.