Open RDmitchell opened 1 year ago
Yes, this feature will be very helpful to optimize the process of mapping data to be sent to BETTER from SEED!
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
instance: seeddemostaging SHA:
When doing a BETTER analysis, BETTER is quite picky about the fields that are sent via the API to do the calculations.
Some of the ESPM fields that it needs are not necessarily mapped according to what BETTER expects, and it can be quite frustrating to try to figure out (iteratively) what the mapping should be.
We can add something on the Mapping screen about it, but it might also be worth having yet another column in Column Settings (??) for BETTER field mappings.
For example, in ESPM here are some default fields that need to be changed for BETTER to have what it needs
ESPM Field: State/Province
BETTER field: State
ESPM field: Property Type - Self Selected
BETTER field: Property Type
and there are probably more.
Or maybe we have a default BETTER mapping profile, like we do for ESPM and BuildingSync ??