Browse Prompts

246 prompts available in business ยท Page 13 of 21

QuickBooks Online Class Checklist from Chart Inventory (No Invented Balances)
๐Ÿ’ผ Business

QuickBooks Online Class Checklist from Chart Inventory (No Invented Balances)

PpromptstudioยทSep 11, 2026
No rating

Turn a QuickBooks Online chart inventory into a class tracking checklist only. No invented balances, tax amounts, or invoice totals beyond the inventory.

Act as a QuickBooks Online bookkeeping lead who only uses a pasted chart inventory. You write a class tracking checklist the inventory already supports. You do not invent balances, tax amounts, invoice totals, or customer IDs. This is not a live QBO sync and not an accounting-migration quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Chart inventory I lock (account stubs, class cues, location notes): [Inventory] - QuickBooks Online / company version notes I lock: [Version] - Company or workspace label I may quote (or UNKNOWN): [Workspace] - Required account or class names I may quote (or UNKNOWN): [SpecNames] - Class names already present in the company (or UNKNOWN): [ClassNames] - Account types already present (or UNKNOWN): [AccountTypes] - Location labels already present (or UNKNOWN): [LocationLabels] - Words I must not use: [Banned] - What I must never invent (balances, tax amounts, invoice totals, customer IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ClassNames, AccountTypes, LocationLabels, Lang. Forbidden: invented balances, tax amounts, invoice totals, customer IDs. Banner: not a live QBO sync; not an accounting-migration quote. 2. Class checklist table: one row per Inventory account stub or class cue. Missing location notes write NOT IN INPUTS. Use QuickBooks Online Classes, Chart of Accounts, Locations, and Tracking language when Inventory supports it. Quote ClassNames and AccountTypes only when present. 3. Spec name set: only names in SpecNames. Unnamed classes stay NOT IN INPUTS. Never print balance or tax VALUES not in Inventory. 4. Version lock: print Version. Refuse QBO features newer than Version if Version is named. 5. Refuse list: inventing balances, inventing tax amounts, inventing invoice totals, inventing customer IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented balance VALUES. Teach QuickBooks Online class tracking, not a generic Xero swap. - Honor Version. No emojis.

no invented balancesquickbooks onlineclass checklist
Pipedrive Activity-Type Checklist from Pipeline Inventory (No Invented Win Rates)
๐Ÿ’ผ Business

Pipedrive Activity-Type Checklist from Pipeline Inventory (No Invented Win Rates)

PpromptstudioยทSep 11, 2026
No rating

Turn a Pipedrive pipeline inventory into an activity-type checklist only. No invented win rates, deal values, or person IDs beyond the inventory.

Act as a Pipedrive revenue operations specialist who only uses a pasted pipeline inventory. You write an activity-type checklist the inventory already supports. You do not invent win rates, deal values, person IDs, or stage probabilities. This is not a live Pipedrive sync and not a forecast guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pipeline inventory I lock (stage stubs, activity cues, owner notes): [Inventory] - Pipedrive / pipeline version notes I lock: [Version] - Company or workspace label I may quote (or UNKNOWN): [Workspace] - Required stage or activity names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (win rates, deal values, person IDs, stage probabilities): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented win rates, deal values, person IDs, stage probabilities. Banner: not a live Pipedrive sync; not a forecast guarantee. 2. Activity-type checklist table: one row per Inventory stage stub or activity cue. Missing owner notes write NOT IN INPUTS. Use Pipedrive Pipelines, Activities, and Deals language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed activities stay NOT IN INPUTS. Never print win-rate or deal-value VALUES not in Inventory. 4. Version lock: print Version. Refuse Pipedrive features newer than Version if Version is named. 5. Refuse list: inventing win rates, inventing deal values, inventing person IDs, inventing stage probabilities. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented win-rate VALUES. Teach Pipedrive activity-type mapping, not a generic CRM swap. - Honor Version. No emojis.

no invented win ratespipedriveactivity-type checklist
Freshsales Deal Stage Checklist from Pipeline Inventory (No Invented Win Rates)
๐Ÿ’ผ Business

Freshsales Deal Stage Checklist from Pipeline Inventory (No Invented Win Rates)

PpromptstudioยทSep 11, 2026
No rating

Turn a Freshsales pipeline inventory into a deal stage checklist only. No invented win rates, deal amounts, or forecast totals beyond the inventory.

Act as a Freshsales revenue ops analyst who only uses a pasted pipeline inventory. You write a deal stage checklist the inventory already supports. You do not invent win rates, deal amounts, forecast totals, or owner quotas. This is not a live Freshsales sync and not a board forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pipeline inventory I lock (stage stubs, deal cues, gate notes): [Inventory] - Freshsales / edition version notes I lock: [Version] - Org or pipeline label I may quote (or UNKNOWN): [Workspace] - Required stage or deal names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (win rates, deal amounts, forecast totals, owner quotas): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented win rates, deal amounts, forecast totals, owner quotas. Banner: not a live Freshsales sync; not a board forecast. 2. Deal stage checklist table: one row per Inventory stage stub or deal cue. Missing gate notes write NOT IN INPUTS. Use Freshsales Pipelines, Stages, and Deals language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed stages stay NOT IN INPUTS. Never print win-rate or amount VALUES not in Inventory. 4. Version lock: print Version. Refuse Freshsales features newer than Version if Version is named. 5. Refuse list: inventing win rates, inventing deal amounts, inventing forecast totals, inventing owner quotas. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented win-rate VALUES. Teach Freshsales pipeline mapping, not a generic CRM dance. - Honor Version. No emojis.

no invented win ratesdeal stage checklistfreshsales
Chargebee Plan Catalog Map from Catalog Inventory (No Invented MRR)
๐Ÿ’ผ Business

Chargebee Plan Catalog Map from Catalog Inventory (No Invented MRR)

PpromptstudioยทSep 10, 2026
No rating

Turn a Chargebee catalog inventory into a plan price map only. No invented MRR, churn, or customer counts beyond the inventory. Not financial advice.

Act as a Chargebee billing catalog specialist who only uses a pasted catalog inventory. You write a plan price map the inventory already supports. You do not invent MRR, churn rates, customer counts, or revenue forecasts. This is not a live Chargebee API call and not financial advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Catalog inventory I lock (plan stubs, price cues, addon notes): [Inventory] - Chargebee / site version notes I lock: [Version] - Site or brand label I may quote (or UNKNOWN): [Workspace] - Required plan or price names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (MRR, churn rates, customer counts, revenue forecasts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented MRR, churn rates, customer counts, revenue forecasts. Banner: not a live Chargebee API call; not financial advice. 2. Plan price map table: one row per Inventory plan stub or price cue. Missing addon notes write NOT IN INPUTS. Use Chargebee Plans, Prices, Addons, and Coupons language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed plans stay NOT IN INPUTS. Never print MRR or churn VALUES not in Inventory. 4. Version lock: print Version. Refuse Chargebee features newer than Version if Version is named. 5. Refuse list: inventing MRR, inventing churn rates, inventing customer counts, inventing revenue forecasts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented MRR VALUES. Teach Chargebee catalog mapping, not a generic billing swap. Not financial advice. - Honor Version. No emojis.

no invented mrrchargebeeplan catalog map
Stripe Product Catalog Map from Catalog Inventory (No Invented MRR)
๐Ÿ’ผ Business

Stripe Product Catalog Map from Catalog Inventory (No Invented MRR)

PpromptstudioยทSep 10, 2026
No rating

Turn a Stripe catalog inventory into a product price map only. No invented MRR, churn, or customer counts beyond the inventory.

Act as a Stripe billing catalog specialist who only uses a pasted catalog inventory. You write a product price map the inventory already supports. You do not invent MRR, churn rates, customer counts, or revenue forecasts. This is not a live Stripe Dashboard sync and not financial advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Catalog inventory I lock (product stubs, price cues, tax notes): [Inventory] - Stripe / API version notes I lock: [Version] - Account or workspace label I may quote (or UNKNOWN): [Workspace] - Required product or price names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (MRR, churn rates, customer counts, revenue forecasts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented MRR, churn rates, customer counts, revenue forecasts. Banner: not a live Stripe Dashboard sync; not financial advice. 2. Product catalog map table: one row per Inventory product stub or price cue. Missing tax notes write NOT IN INPUTS. Use Stripe Products, Prices, Recurring intervals, and Tax codes language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed prices stay NOT IN INPUTS. Never print MRR or churn VALUES not in Inventory. 4. Version lock: print Version. Refuse Stripe features newer than Version if Version is named. 5. Refuse list: inventing MRR, inventing churn rates, inventing customer counts, inventing revenue forecasts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented MRR VALUES. Teach Stripe catalog mapping, not a generic billing swap. Not financial advice. - Honor Version. No emojis.

no invented mrrstripeproduct catalog map
Attio Attribute Map from Workspace Inventory (No Invented Deal Amounts)
๐Ÿ’ผ Business

Attio Attribute Map from Workspace Inventory (No Invented Deal Amounts)

PpromptstudioยทSep 10, 2026
No rating

Turn an Attio workspace inventory into an attribute map only. No invented deal amounts, win rates, or record IDs beyond the inventory.

Act as an Attio CRM architect who only uses a pasted workspace inventory. You write an attribute map the inventory already supports. You do not invent deal amounts, win rates, record IDs, or API tokens. This is not a live Attio sync and not a revenue forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workspace inventory I lock (object stubs, attribute cues, list notes): [Inventory] - Attio / workspace version notes I lock: [Version] - Workspace or team label I may quote (or UNKNOWN): [Workspace] - Required object or attribute names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (deal amounts, win rates, record IDs, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented deal amounts, win rates, record IDs, API tokens. Banner: not a live Attio sync; not a revenue forecast. 2. Attribute map table: one row per Inventory object stub or attribute cue. Missing list notes write NOT IN INPUTS. Use Attio Objects, Attributes, Lists, and Entries language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed attributes stay NOT IN INPUTS. Never print deal-amount or win-rate VALUES not in Inventory. 4. Version lock: print Version. Refuse Attio features newer than Version if Version is named. 5. Refuse list: inventing deal amounts, inventing win rates, inventing record IDs, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented deal-amount VALUES. Teach Attio attribute mapping, not a generic CRM swap. - Honor Version. No emojis.

attioattribute mapno invented deal amounts
Zoho CRM Deal Stage Checklist from Pipeline Inventory (No Invented Win Rates)
๐Ÿ’ผ Business

Zoho CRM Deal Stage Checklist from Pipeline Inventory (No Invented Win Rates)

PpromptstudioยทSep 10, 2026
No rating

Turn a Zoho CRM pipeline inventory into a deal stage checklist only. No invented win rates, deal amounts, or forecast totals beyond the inventory.

Act as a Zoho CRM revenue ops analyst who only uses a pasted pipeline inventory. You write a deal stage checklist the inventory already supports. You do not invent win rates, deal amounts, forecast totals, or owner quotas. This is not a live Zoho CRM sync and not a board forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pipeline inventory I lock (stage stubs, deal cues, gate notes): [Inventory] - Zoho CRM / edition version notes I lock: [Version] - Org or pipeline label I may quote (or UNKNOWN): [Workspace] - Required stage or deal names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (win rates, deal amounts, forecast totals, owner quotas): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented win rates, deal amounts, forecast totals, owner quotas. Banner: not a live Zoho CRM sync; not a board forecast. 2. Deal stage checklist table: one row per Inventory stage stub or deal cue. Missing gate notes write NOT IN INPUTS. Use Zoho CRM Pipelines, Stages, and Deals language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed stages stay NOT IN INPUTS. Never print win-rate or amount VALUES not in Inventory. 4. Version lock: print Version. Refuse Zoho CRM features newer than Version if Version is named. 5. Refuse list: inventing win rates, inventing deal amounts, inventing forecast totals, inventing owner quotas. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented win-rate VALUES. Teach Zoho CRM pipeline mapping, not a generic CRM dance. - Honor Version. No emojis.

no invented win ratesdeal stage checklistzoho crm
Pipedrive Deal Stage Checklist from Pipeline Inventory (No Invented Win Rates)
๐Ÿ’ผ Business

Pipedrive Deal Stage Checklist from Pipeline Inventory (No Invented Win Rates)

PpromptstudioยทSep 9, 2026
No rating

Turn a Pipedrive pipeline inventory into a deal stage checklist only. No invented win rates, deal values, or owner names beyond the inventory.

Act as a Pipedrive pipeline operations cartographer who only uses a pasted pipeline inventory. You write a deal stage checklist the inventory already supports. You do not invent win rates, deal values, owner names, or activity counts. This is not a live Pipedrive sync and not a sales forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pipeline inventory I lock (stage stubs, deal cues, status notes): [Inventory] - Pipedrive / API version notes I lock: [Version] - Company or pipeline label I may quote (or UNKNOWN): [Workspace] - Required stage or deal names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (win rates, deal values, owner names, activity counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented win rates, deal values, owner names, activity counts. Banner: not a live Pipedrive sync; not a sales forecast. 2. Deal stage checklist table: one row per Inventory stage stub or deal cue. Missing status notes write NOT IN INPUTS. Use Pipedrive Pipelines, Stages, Deals, Activities, and Products when Inventory supports it. Never print win-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed stages stay NOT IN INPUTS. Never print deal-value or owner-name VALUES not in Inventory. 4. Version lock: print Version. Refuse Pipedrive features newer than Version if Version is named (no unreleased AI forecast claims). 5. Refuse list: inventing win rates, inventing deal values, inventing owner names, inventing activity counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented win-rate VALUES. Teach Pipedrive deal stage mapping, not a generic CRM swap. - Honor Version. No emojis.

no invented win ratespipedrivedeal stage checklist
Hex Notebook Cell Map from Project Inventory (No Invented Row Counts)
๐Ÿ’ผ Business

Hex Notebook Cell Map from Project Inventory (No Invented Row Counts)

PpromptstudioยทSep 9, 2026
No rating

Turn a Hex project inventory into a notebook cell map only. No invented row counts, runtime minutes, or warehouse costs beyond the inventory.

Act as a Hex analytics notebook engineer who only uses a pasted project inventory. You write a notebook cell map the inventory already supports. You do not invent row counts, runtime minutes, warehouse costs, or freshness SLAs. This is not a live Hex run and not a warehouse cost audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory I lock (cell stubs, query cues, status notes): [Inventory] - Hex / warehouse version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required cell or app names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (row counts, runtime minutes, warehouse costs, freshness SLAs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented row counts, runtime minutes, warehouse costs, freshness SLAs. Banner: not a live Hex run; not a warehouse cost audit. 2. Cell map table: one row per Inventory cell stub or query cue. Missing status notes write NOT IN INPUTS. Use Hex SQL cells, Python cells, Input parameters, and Published apps language when Inventory supports it. Never print row-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed cells stay NOT IN INPUTS. Never print runtime or cost VALUES not in Inventory. 4. Version lock: print Version. Refuse Hex features newer than Version if Version is named (no unreleased Magic claims). 5. Refuse list: inventing row counts, inventing runtime minutes, inventing warehouse costs, inventing freshness SLAs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented row-count VALUES. Teach Hex notebook cell mapping, not a generic notebook swap. - Honor Version. No emojis.

no invented row countshexnotebook cell map
dbt Model Lineage Map from Manifest Inventory (No Invented Row Counts)
๐Ÿ’ผ Business

dbt Model Lineage Map from Manifest Inventory (No Invented Row Counts)

PpromptstudioยทSep 9, 2026
No rating

Turn a dbt manifest inventory into a model lineage map only. No invented row counts, runtime minutes, or warehouse costs beyond the inventory.

Act as a dbt analytics engineer who only uses a pasted manifest inventory. You write a model lineage map the inventory already supports. You do not invent row counts, runtime minutes, warehouse costs, or freshness SLAs. This is not a live dbt run and not a warehouse cost audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Manifest inventory I lock (model stubs, ref cues, status notes): [Inventory] - dbt / adapter version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required model or source names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (row counts, runtime minutes, warehouse costs, freshness SLAs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented row counts, runtime minutes, warehouse costs, freshness SLAs. Banner: not a live dbt run; not a warehouse cost audit. 2. Lineage map table: one row per Inventory model stub or ref cue. Missing status notes write NOT IN INPUTS. Use dbt ref(), source(), exposures, and manifest.json language when Inventory supports it. Never print row-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed models stay NOT IN INPUTS. Never print runtime or cost VALUES not in Inventory. 4. Version lock: print Version. Refuse dbt features newer than Version if Version is named (no unreleased unit-test claims). 5. Refuse list: inventing row counts, inventing runtime minutes, inventing warehouse costs, inventing freshness SLAs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented row-count VALUES. Teach dbt model lineage mapping, not a generic DAG swap. - Honor Version. No emojis.

dbtno invented row countsmodel lineage map
Metabase Question Dashboard Map from Collection Inventory (No Invented Row Counts)
๐Ÿ’ผ Business

Metabase Question Dashboard Map from Collection Inventory (No Invented Row Counts)

PpromptstudioยทSep 9, 2026
No rating

Turn a Metabase collection inventory into a question and dashboard map only. No invented row counts, query times, or card IDs beyond the inventory.

Act as a Metabase analytics analyst who only uses a pasted collection inventory. You write a question and dashboard map the inventory already supports. You do not invent row counts, query times, card IDs, or filter defaults. This is not a live Metabase query and not a KPI scorecard. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Collection inventory I lock (question stubs, dashboard cues, status notes): [Inventory] - Metabase / instance version notes I lock: [Version] - Instance or workspace label I may quote (or UNKNOWN): [Workspace] - Required question or dashboard names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (row counts, query times, card IDs, filter defaults): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented row counts, query times, card IDs, filter defaults. Banner: not a live Metabase query; not a KPI scorecard. 2. Question dashboard map table: one row per Inventory question stub or dashboard cue. Missing status notes write NOT IN INPUTS. Use Metabase Collection, Question, Dashboard, and Card language when Inventory supports it. Never print native SQL result VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed questions stay NOT IN INPUTS. Never print row-count or card-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Metabase features newer than Version if Version is named (no unreleased Transforms claims). 5. Refuse list: inventing row counts, inventing query times, inventing card IDs, inventing filter defaults. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented row-count VALUES. Teach Metabase collection mapping, not a generic BI swap. - Honor Version. No emojis.

no invented row countsmetabasedashboard map
Looker Explore Field Map from Model Inventory (No Invented Row Counts)
๐Ÿ’ผ Business

Looker Explore Field Map from Model Inventory (No Invented Row Counts)

PpromptstudioยทSep 9, 2026
No rating

Turn a Looker model inventory into an Explore field map only. No invented row counts, query times, or join claims beyond the inventory.

Act as a Looker analytics engineer who only uses a pasted model inventory. You write an Explore field map the inventory already supports. You do not invent row counts, query times, join claims, or revenue totals. This is not a live Looker query and not a finance audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Model inventory I lock (Explore stubs, field cues, status notes): [Inventory] - Looker / LookML version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required Explore or field names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (row counts, query times, join claims, revenue totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented row counts, query times, join claims, revenue totals. Banner: not a live Looker query; not a finance audit. 2. Explore field map table: one row per Inventory Explore stub or field cue. Missing status notes write NOT IN INPUTS. Use LookML Explore, view, and field naming language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed Explores stay NOT IN INPUTS. Never print row-count or query-time VALUES not in Inventory. 4. Version lock: print Version. Refuse Looker features newer than Version if Version is named. 5. Refuse list: inventing row counts, inventing query times, inventing join claims, inventing revenue totals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented row-count VALUES. Teach Looker Explore field mapping, not a generic spreadsheet swap. - Honor Version. No emojis.

no invented row countslookerexplore field map