First, and foremost, RC2 is out and available already that should fix any remaining UI issues.
Second, the action behaves differently because:
1. If you are not shown the ability to define a range is because you already have a Dynamic range created.
2. If it is asking you to create a range, it means you dont previously have a dynamic range created.
We know this is not ideal UX< but this is a problem that UX needs to fix so we can fix. This is being tracked separately.
Hi Dann,
First, and foremost, RC2 is out and available already that should fix any remaining UI issues.
Second, the action behaves differently because:
1. If you are not shown the ability to define a range is because you already have a Dynamic range created.
2. If it is asking you to create a range, it means you dont previously have a dynamic range created.
We know this is not ideal UX< but this is a problem that UX needs to fix so we can fix. This is being tracked separately.
Thanks