Closed RDmitchell closed 2 years ago
@nllong -- This is a tricky request because there are so many ESPM fields that are possible. The defaults currently there are OK, not great, but probably passable for now.
Would it be possible to add these three also?
I can take a look at this
Hey @RDmitchell, when trying to reproduce the bug on production (https://seedv2.lbl.gov/) "Property Name" and "City" populated with the "Property Manager Defaults" profile. Could you pass along the file you were testing with?
instance: dev1 SHA: 400ca8895
I don't see this change implemented in this version on dev1
Here is a link to a file to test with 2 - example-data-ESPM-Alerts-UBID.xlsx
Instance: dev1 SHA: 1.449f54dcf
Property ID is still not being mapped to PM Property ID, same with Property Name and City, to name a few.
@nllong thinks that possibly ESPM had a different name for Property ID and that is what SEED is mapping to PM Property ID.
So we need to figure out how to fix that.
I'm having trouble duplicating this locally (see below). Testing on production might be more telling
@perryr16 -- interesting. Maybe it has to do with the mapping for my particular org. Let me test on a brand new org and see if it works then.
Instance: seedv2 production SHA: 09736c1d6
OK, so it definitely works properly for a completely new org without any previous import/mapping history.
So I am going to close this issue.
Describe the bug The current "Portfolio Manager Defaults" Column Mapping Profile does not do a good job of actually mapping Portfolio Manager fields.
Expected Behavior I expected that selecting that mapping profile would map the ESPM fields in the file I was importing
Actual Behavior Only a few fields were actually mapped when I selected that mapping (using the JCC ESPM file from #2808)
Steps to Reproduce
Here is a more reasonable mapping, but basically we need to go through the standard ESPM fields and map them to SEED fields.
I am happy to help with this task.
Instance Information
Instance: dev1 SHA: 24b503d2d
Additional Context none