Skip to main content

layoutLibraryItemUsageDetail

No description

layoutLibraryItemUsageDetail(
id: ID!
): LayoutLibraryItemUsageDetail!

Arguments​

layoutLibraryItemUsageDetail.id ● ID! non-null scalar​

Type​

LayoutLibraryItemUsageDetail object​

WHICH assets depend on one Library node, for the Where Used dialog — the rows behind the count LayoutLibraryItemUsage returns.

A SECOND FIELD rather than buckets on that type, because a @field resolver computes its whole payload whatever the client selected: folding these in would make the padlock and the palette restriction — both of which want counts only, on every builder request — pay for up to four extra asset queries they never read.

Buckets, not one list, because that is the shared ObjectUsageDialog contract: it renders one accordion per non-empty bucket and already knows these four keys. Every entry is an asset in THIS product holding a live reference; trashed assets are omitted, so this can list fewer than total until the index is reconciled on delete (see LibraryNodeUsageScanner).

Product

PricingFAQPaminga vs. MarketoMigration CenterMarketo to Paminga TranslatorMarketo Alternative
Paminga Logo
LinkedInFacebookXYouTube
ISO 27001 CompliantSOC 2 Compliant

Built with pride in Denver, Colorado, USA

Copyright © Paminga, Inc. 2026
All rights reserved. Various trademarks held by their respective owners.