- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎May 20, 2024 01:41 PM
Odd one, but I've noticed it a couple of times in the last week, so I wonder if it's a quirk of a new update.
Basically I have a Status dropdown with a default option applied, called Planned
One view that has some filters, including "If {dropdown} = ARCHIVE: Amendment"
There is no grouping for the dropdown options in this view.
Yet, when I create a new record it defaults to ARCHIVE: Amendment.
This is how the filters are setup.
Anyone know why this is? It's very frustrating. Is this a bug?
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎May 21, 2024 12:56 AM
When we create a record in a view with a specific filter for a dropdown field, new records that get created are created with that filter value automatically. To test this, try creating a new view where the only filter is "Status = Archive: Amendment" and creating records in that view and you should see the same behaviour
This functionality's overriding the "Default" value in this instance I reckon
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎May 21, 2024 12:56 AM
When we create a record in a view with a specific filter for a dropdown field, new records that get created are created with that filter value automatically. To test this, try creating a new view where the only filter is "Status = Archive: Amendment" and creating records in that view and you should see the same behaviour
This functionality's overriding the "Default" value in this instance I reckon
