Hi,
Thank you for contacting us and I'd be happy to assist.
Whenever any content editor/page builder other than Blocks is being used, the workflow would remain the same as it was before the Blocks and WordPress Gutenberg.
You can insert Toolset elements like views and maps etc, using the "Fields and Text" button or by adding the relevant shortcodes directly.
For example, you'll find the "Fields and Text" button available on top, when you'll add the "Text Editor" module from the Beaver Builder's editor.
( example screenshot: hidden link )
The map can either be inserted through this "Fields and Text" button or by using the "wpv-map-render" shortcode, directly:
https://toolset.com/documentation/programmer-reference/maps/maps-shortcodes/
For the map and the map markers from post view to work together, the page just needs:
a). The "wpv-map-render" shortcode to generate a map
b). The "wpv-map-marker" shortcode that brings in location/coordinates information from each post's address field.
( this will need to be inside the post view's loop )
As long as the "map_id" attribute values are the same in both these shortcodes, the map will know that for map markers, the source should be the post view.
As for the post view, you'll create it using the Classic editor and not the Blocks editor. You can go to WP Admin -> Toolset -> Settings -> General and make sure that "Show both the legacy and Blocks interface and let me choose which to use for each item I build" option is selected for the "Editing experience" field.
After that, you'll see the views management screen at WP Admin -> Toolset -> Views, from where you'll be able to create views using the classic editor.
I hope this helps and please let me know if you need any further assistance around this.
regards,
Waqar