You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.
Is your feature request related to a problem? Please describe.
The original iteration of query sources was a query per property; however, these can not be used as a primary source because they need a WHERE clause and they lead to inefficiencies.
Describe the solution you'd like.
A new query source should have a query at the root. The SELECTed columns would be properties.
These should produce the data that is written to the Records and then sync'd as they are now.
This source would be able to be used as a primary source or incorporate current property values and be a secondary source.
It should be optional to do things incrementally as this is not always available.
In the ideal case, it would also be able to be used in the Config UI and sample profiles.
Describe an alternate solution.
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Is your feature request related to a problem? Please describe.
The original iteration of query sources was a query per property; however, these can not be used as a primary source because they need a
WHERE
clause and they lead to inefficiencies.Describe the solution you'd like.
A new query source should have a query at the root. The
SELECT
ed columns would be properties.These should produce the data that is written to the Records and then sync'd as they are now.
This source would be able to be used as a primary source or incorporate current property values and be a secondary source.
It should be optional to do things incrementally as this is not always available.
In the ideal case, it would also be able to be used in the Config UI and sample profiles.
Describe an alternate solution.
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: