Best practice regarding of Design RecordType

Hello:

I am trying to create a RecordType synchronized with a web-service.  One of the data objects obtained doesn't always have the same number of sub-data points (see nutrients in the image).  In order for me to store the nutrients values, right now, I am creating 20 columns (assuming a max) and using a forEach to store each value.  Is there a better way to do this?

Thank you.

  

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    Are the nutrients of any importance? I mean in terms of relationship? If not, just store them as a comma-separated string. If yes, I think you could create a separate record with just holds the nutrients and their relationship to the product. You could even create a many-many relationship using a third record.

    But I am not sure whether this is the best use case for a synced record. Did you consider making it a non-synced record, and just query the data directly from the API?

Reply
  • 0
    Certified Lead Developer

    Are the nutrients of any importance? I mean in terms of relationship? If not, just store them as a comma-separated string. If yes, I think you could create a separate record with just holds the nutrients and their relationship to the product. You could even create a many-many relationship using a third record.

    But I am not sure whether this is the best use case for a synced record. Did you consider making it a non-synced record, and just query the data directly from the API?

Children
  • Stefan:

    The nutrient values has significant importance.  Need the data to analyze the product.  Right now, I am doing two tables - one for the product 'profile' info and another with the nutrient values - with UPC connecting the two tables.

    I am thinking about the non-synced record but was following the SpaceX tutorial to learn about webIntegration/Service-backed records.

    Thanks for the feedback - always appreciate it.

    Ma