Ah, I see, @faismoibg. So, this isn’t really documented (partly because I’ve not really tested List Shifter with date ranges), but basically, List Shifter doesn’t properly support the date range data type.
This is why you’re getting that error about ListShifter KW A in the console and also in the debugger. (What’s happening is that ListShifter KW A is basically crashing and so never initializes and will not do anything useful.)
The solution in your case (I’m talking about the page you pointed me to: Faismoibg) is to feed that List Shifter not with RepeatingGroup Rendez-vous's List of Rendez-vouses:each item's Ceneau
, but make the List Shifter’s Data Type of List Rendez-vous
and feed it with RepeatingGroup Rendez-vous's List of Rendez-vouses
.
Then, when you’re iterating over List Shifter A, the Current Iteration Item will be a Rendez-vous, but you can get the item’s date range by Current Iteration Item's Ceneau
.
Further:
I see where you are also trying to simply test the Iterate feature using List Shifter B. You’ve currently got List Shifter B set up correctly, but over in your workflow attached to the “GO” button (which you have disabled right now), you are attempting to fire the BEGIN ITERATE action at List Shifter A (which is broken and will not respond).
To test your “B” workflow you need to fire BEGIN Iterate at ListShifter B. Like so (select List Shifter B not List Shifter A):
As far as why List Shifter does not support the Date Range data type properly:
This comes down to an inconsistency in Bubble’s plugin API. We publish exposed states (such as List Shifter’s Original List) with a function called publishState()
. If an exposed state is a List and that output is supposed to be an empty list (the list has no items), we can in almost all cases tell publishState()
to push an empty array ([]
in JavaScript), which is what List Shifter does.
However, in the case of Date Ranges (and probably Numeric Ranges), publishState() it seems not to interpret as just make the output empty. Instead, it throws an error (“expected a date range but got an object instead”).
This inconsistency is basically a bug in Bubble’s plug-in API. While I could work around it (and I might fix that in a future update), it’s rather a pain to do so and I can’t commit to fixing it in any specific time-frame. But I have run into this before and should probably report it to Bubble as a bug in the plugin API.
In your case, what I suggest above will work just fine though!