Mark Aceto

I'll submit this as a bug if I can replicate it in one of my files. Us.

The goal is to take the worksheet editing and formatting out of VW. Also curious how VW manages XLSX tabs because I typically use Excel/Sheets as a "database". First tab is always "Entry", last tab is "Validation", and then I'll create a bunch of tabs in between that are pivot tables rearranging the data.

@michaelkis there a risk of user error with this method? I always think of VW database rows as dumb pivot tables. For example, if I add a new object that needs to be counted, the DB will automatically find it, recalc, and expand the number of rows. However, for a spreadsheet (not a database), do I have to manually add that object?

@michaelk and @Sam Jones I thought there was an option to reference an external spreadsheet on import...

Now I finally know what Pon De Floor means. Here's the link to the help file (for bookmarking): https://developer.vectorworks.net/index.php/Search_Criteria_Format

Alas, half-baked. While you can create a Saved View inside an edit mode, you cannot create a Viewport from in there. So it's really just the drawing origin that works.

Rules were meant to be broken 😎

This is probably an enhancement request but man it would be cool if the clip cube had its own plane like a hanging position or symbol definition, so you could isolate scenery or whatever you want with your own 0,0 (especially since you can create a clip cube by selecting the objects you want to isolate). Maybe creating a few fake hanging positions is a workaround? I recall some folks telling me they just use a rectangle for a floor package.

Unreal / Twinmotion

you can but it's Russian roulette another one that drives me crazy is selecting a cell i want to edit when i'm in a database header row...

it's neither here nor there (literally) because i just tested it (my hopes and dreams are crushed) 2 options: try to control as much as possible with section viewport OIP settings, properties... as much as i cringe to say this (i have a buddy that does this all the time), take a screenshot, and import the image to a sheet layer (just threw up in my mouth and swallowed a little) to me, this is the nail in the coffin about how the clip cube workflow fails documentation (or rather documentation fails the clip cube)

could you mock up what you hope to achieve, or share a screenshot that shows what's missing?

For context, there are 2 hopes: I would like to take the worksheets out of VW where I can do so much more (pivot tables), so much faster (formatting), and then reference them back into VW This would also help me manage a larger library of worksheets If nothing else, I might just export them, play with them, and then bring them back in However, it seems like the database header row formulas get lost in the plot export The shop wants to streamline shop orders across multiple projects I caveated the dream of a magic bullet shooting for the moon but there's probably a happy medium that will at least improve quality of life for them

@michaelk is there a way to reference an external spreadsheet or database (like filemaker)?

the reason it won't let you manually enter spares in those rows of column C is because they're a database, so you either have to auto calc every row in column C (as in my screenshots) or add "dumb" spreadsheet rows below the database (which would quickly get annoying)

taking what michael said, how's this:

in column C, he wants to manually add (or auto calc a percentage) spares

You can control depth with the section advanced properties. However you should be able to control most of that with the clip cube as well. For example, I affectionally call this a 3D RCP aka C-3PO (clipped from all 6 sides to isolate a cut “plane” of roughly 4’ to 15’):

No but I’ve learned that the general rule of thumb is: annotations in plan view go on the design layer annotations in 3D views go on the annotation layer of the SLVP Multiple pane view helps with the back-and-forth between design and sheet layers of that workflow (design layers on the left; sheet layer on the right). Also a little bit of extra classing to control viewport visibilities. Just be thankful you’re not an architect that’s plating up a 200 sheet drawing set. We have it easy.

One of the best-kept secrets by the VW marketing dept. Think it’s actually been around since 2021 but the command had to be manually added to your workspace. I use it for all the data tags that I’ve been gradually adding to my user library. I always check both columns to create labels. Continuing to build… continuity… across all data tag styles.

ok i finally get it now it's one poly for the entire data tag (almost like a crop object for a viewport)

btw for context, the only way i know how to put a bounding box around text is to use the callout tool (and then minimize the leader) hence drawing a box (or other poly) around the text field meanwhile in my inbox today:

i don't think that works for a box around the text field been messing around with a data tag i have open in this file i'm working on:

gorgeous section line hatch

i need to do this all the time, so this is great! we can beat this together