search

KingdomFirst / Excavator

We have now released Bulldozer on GitHub. Bulldozer is the super-powerful big brother to Excavator. Because Bulldozer is now published on GitHub we will no longer be supporting Excavator. Thank you for all the support here!
https://github.com/KingdomFirst/Bulldozer
19 stars 20 forks source link

'Object reference not set to an instance of an object.' after successful second individuals import... #189

Closed knolly42 closed 6 years ago

knolly42 commented 6 years ago

Hi, I'm finding that when I search for a successfully imported person in Rock, their detail page opens to an error page instead?

They appear in the correct family (via other family member profiles) but if I click them I'm getting the error.

Any idea why this happens on the second import only and not the first? and any idea why it is happening please?

Families for incremental additions are added first, then individuals added in a separate import.

Hope you can advise please?

thanks for your efforts with this wonderful project 👍

knolly42 commented 6 years ago

Just ran a check on PersonAlias - seems that if you run a secondary import then no PersonAlias is created, hence the issue

rutledgek commented 6 years ago

What error do you get?

knolly42 wrote:

Just ran a check on PersonAlias - seems that if you run a secondary import then no PersonAlias is created, hence the issue

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NewSpring/Excavator/issues/189#issuecomment-361728765, or mute the thread https://github.com/notifications/unsubscribe-auth/AXQAnJEA30eNuTSDIWINSojOOgnrUz43ks5tP3-xgaJpZM4Ryw-_.

dcs619 commented 6 years ago

I can confirm this behavior, but if you import the individuals first with a secondary import, then family, it will create the PersonAlias correctly.