Welcome! This forum has a treasure trove of great info – Scouters helping Scouters! Just a heads up, though - all content, information, and opinions shared on this forum are those of the author, not the BSA.
I have the Scoutbook Feature Assistant v0.49.0.10 installed and have access to the Export Calendar Events to CSV feature under Events on My Dashboard page. After selecting that I get the Choose Data Range to export pop-up window in which I enter a start and end date and then select Export Event File. When I do this the next pop-up I get indicates: scoutbook.scouting.org says: Please log into Internet Advancement in a separate tab to enable access for this feature.
This is where I am stuck. I am already logged into scoutbook, and therefore Internet Advancement. I have tried opening a new tab and logging in and out, but that does not solve it either. I have not been able to figure out what it needs for me to get access to the requested CSV file. Can you help me?
The problem you likely experienced is a difference between sessions in Scoutbook and Internet Advancement.
They are separate websites with separate session timeouts; even though they share a username and password. If you are active in Scoutbook for more than a half hour or so, and were in Scoutbook Plus/Internet Advancement at the start, Internet Advancements session can expire. This can cause the message. Simply logging back in to Internet Advancement resolves it… until the next timeout.
I launched chome and logged into https://advancements.scouting.org/. I then opened another tab and logged into https://scoutbook.scouting.org/ and reloaded the Feature Assistant Extension (in order to get access to the Export Calendar Events to CSV option under Events). After selecting that I get the Choose Data Range to export pop-up window in which I enter a start and end date and then select Export Event File. When I do this the next pop-up I get indicates: scoutbook.scouting.org says: Please log into Internet Advancement in a separate tab to enable access for this feature.
Unfortunately, it is the same as the original experience. I am doing this within 2 minutes of each other so the sessions should be within the timeouts. I tried logging in and out of both multiple times without success, so I am thinking this is not the root cause of the problem…