Skin CMS
Ext. linksLegal
Skin CMS
Skin CMS
  • Quick Start
  • 3DVista Skin Components
    • 3DVista Label
    • 3DVista Multiline
    • 3DVista Image
    • 3DVista WebFrame
    • 3DVista Button
  • Dynamic Photo Album
  • Optional Features
    • 🟢Mobile sync
    • 🟢Map multiple 3DVista skin components
    • 🟠Attribute Styling
    • 🟠3DVista Functions
      • Show or hide Hotspots
  • Videos
    • All videos • Youtube Playlist
    • Collaborate in Airtable
    • Right click edit this content
    • Linked records to Categorize
    • Dynamic buy button with stripe
  • Common errors
Powered by GitBook
On this page

Was this helpful?

  1. Optional Features

Attribute Styling

PreviousMap multiple 3DVista skin componentsNext3DVista Functions

Last updated 9 months ago

Was this helpful?

Mapping attributes is similar to mappings values. Let's consider a simple mapping of an Airtable field called "Product title" to a 3DVista component called "Title":

This results in the Airtable record's value being mapped to the "Title" component:

Mapping attributes is very similar. Let's say we want to change the color of the Title and we want to use a value from Airtable. The color can be computed, for example depending on the product's status it can be green if the product is available or red if the product is sold out - we can use a formula field to achieve this:

Let's create a new field "Product title color" with a computed value depending on the value from the field "stock"

Let's map the new "Product title color" to the component "Title" but this time to an attribute "fontColor"

Voilà, there we have the color of the "Title" component changed:

With attributes you can change the component's style, position, alignment etc.

ðŸŸ