I'm looking to see if there is further development on the extract schedule feature, right now, I tried to extract this schedule, it will not recognize the columns and make everything into 2 columns only. I want to be able to select certain columns and then have it create conditions into an existing takeoff folder.

Have you tried this yet? I don't htink you can make it go into the yellow folders tho, only grey folders.

Batch import can make yellow folders; you just need to change Assembly to Folder then Copy/Paste your names.

what columns is it breaking out to 2?
This is what I am talking about when using the extract schedule feature.

I selected the entire schedule
I dont know how the batch insert works with a schedule on the plans
Yes, extract schedule tool desperately needs improvements, I've been waiting for a year for it to be enhanced so that it can do things such as this:

Batch insert still does not let you map to those fields either, so I can't even use the workarounds mentioned above by Kyle & Shawn
Story time:
I actually got into hot water with my boss yesterday because I was working on a complex building with a ton of beams and was already late on submitting the bid. The extract schedule tool hasn't been enhanced so that you could do things like what Jeffery is asking (and the functionality I asked for in this example above) where we can map the text it extracts, and I didn't have time to manually assign the 50+ beams it extracted and just left them exactly how zz extracted them.
Once I finally finished my takeoff and the time came to port everything to my Excel template, I had to scramble and format/convert things to decimals, and due to being in a rush, I had a keystroke error where I missed a decimal point on what just so happened to be one of the longest beams on the project. Instead of entering .92 (11 inches) for the beam's height, I put in 92 (which came in as feet). My estimate came in way too high as you can imagine on account of this 91 foot error and got a tongue lashing from boss man.
If I had been able to get those beams mapped directly into the width & depth fields of the takeoff object measurement properties, I would have been able to quickly generate a semi accurate totals report in zz to compare it to my Excel summary, and could have immediately identified that something was way off in my quantities. But because there were so many beams on this project and I was pressed for time, I never manually entered them into those fields, so I couldn't fall back on my ZZ data to discover this manual user error I created in Excel.
Please get this enhanced before I get fired 😫
when you use the extract schedule feature, you can highlight the Text it pulls up then CTRL+C, go to batch insert takeoff and CTRL+V in the name section. I do agree that the extract tool needs some improvements however, for the time being this is how I create folders.
@Shawn If a user wanted linear objects & counts to appear on their takeoffs in their actual dimensions, they still need to go in and edit the takeoff properties manually one by one since batch insert doesn't have those columns for takeoff object dimensions. And that's fine if you only have a dozen or so to enter. But on monster projects it just becomes a time consuming nightmare on top of all the other things you need to contend with
I completely understand that.
Where did you Find "Count W / Length & Width?
Sorry, going down a rabbit hole here.
@Jes, you could set it up something like this. Granted, I had to do some back work to get to this, I took your list and asked CoPilot to change the formatting and split each into separate columns. then I Created a list called beams and did a batch import. I also had to create the "beam Length & Beam Width" to be able to import it. The custom properties on the count are inheriting the numbers based on the product selected. Like I said, rabbit hole. 🤣

Would this work at all or did I go in a totally different direction?
@Shawn
-->
-->
-->

I'm not sure how doing this on the product level would help if the user wants the takeoff objects to match actual dimensions on screen. But even if they don't need that, they would still need to add all sorts of formulas & assemblies in order to be able to create takeoff reports with summaries that total out correctly if they use product lists to insert the dimensions

That's pretty cool. So you changed those fields to use formulas, and then you have a formula setup in there to pull those dimensions from the imported product list you manually created. Not a terrible work around for the time being I suppose
Once you have the Count saved as a tool, it would become less of work. But yes, the initial setup will take a bit of work.
Sorry I took over this thread. 🤣