# GBVIMS+ v1.5 Incident Recorder Export Issue

**URL:** <https://support.primero.org/forum/t/gbvims-v1-5-incident-recorder-export-issue/438>\
**Category:** GBVIMS\
**Tags:** v1-5-b\
**Created:** [May 25, 2021, 9:09pm UTC](https://support.primero.org/forum/t/gbvims-v1-5-incident-recorder-export-issue/438 "2021-05-25T21:09:59Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![megan.obrien](https://support.primero.org/forum/letter_avatar_proxy/v4/letter/m/7feea3/32.png) [@megan.obrien](https://support.primero.org/forum/u/megan.obrien)\
**Post date:** [May 25, 2021, 9:09pm UTC](https://support.primero.org/forum/t/gbvims-v1-5-incident-recorder-export-issue/438/1 "2021-05-25T21:09:59Z")

</div>

When I export the Incident Recorder, the answers for the question, “Does the client want to pursue legal action?” are not being populated. I have confirmed that caseworkers are selecting answers, but they are still not appearing in the Incident Recorder.

---

<div class="post-metadata">

**Author:** ![irlawrence](https://support.primero.org/forum/user_avatar/support.primero.org/irlawrence/32/8_2.png) [@irlawrence](https://support.primero.org/forum/u/irlawrence)\
**Post date:** [May 26, 2021, 7:33pm UTC](https://support.primero.org/forum/t/gbvims-v1-5-incident-recorder-export-issue/438/2 "2021-05-26T19:33:48Z")

</div>

The field pursue\_legal\_action uses the lookup lookup-yes-no-undecided. The addition of undecided meant that this is coming as a string instead of as a boolean. There is some logic in the application that converts lookup-yes-no and lookup-yes-no-undecided to use boolean true/false instead of string yes/no so we will need to use that. We are working on this fix atm

---

<div class="post-metadata">

**Author:** ![irlawrence](https://support.primero.org/forum/user_avatar/support.primero.org/irlawrence/32/8_2.png) [@irlawrence](https://support.primero.org/forum/u/irlawrence)\
**Post date:** [June 2, 2021, 12:27pm UTC](https://support.primero.org/forum/t/gbvims-v1-5-incident-recorder-export-issue/438/3 "2021-06-02T12:27:09Z")

</div>

This has already been fixed in versions above 1.6

> <https://github.com/primeroIMS/primero/commit/929ff873e85af366d499bffb234d99c090c56bb4>

so we will backport it to 1.5

---

<div class="post-metadata">

**Author:** ![megan.obrien](https://support.primero.org/forum/letter_avatar_proxy/v4/letter/m/7feea3/32.png) [@megan.obrien](https://support.primero.org/forum/u/megan.obrien)\
**Post date:** [June 2, 2021, 1:19pm UTC](https://support.primero.org/forum/t/gbvims-v1-5-incident-recorder-export-issue/438/4 "2021-06-02T13:19:13Z")

</div>

That’s great news! Will you please flag when this fix is ready for 1.5? Also, will you please share the steps to apply these fixes (when ready)? Thank you!

---

<div class="post-metadata">

**Author:** ![irlawrence](https://support.primero.org/forum/user_avatar/support.primero.org/irlawrence/32/8_2.png) [@irlawrence](https://support.primero.org/forum/u/irlawrence)\
**Post date:** [June 2, 2021, 4:09pm UTC](https://support.primero.org/forum/t/gbvims-v1-5-incident-recorder-export-issue/438/5 "2021-06-02T16:09:45Z")

</div>

Merged [Fix legal\_couseling value handling by rbelem · Pull Request #15 · primeroIMS/primero · GitHub](https://github.com/primeroIMS/primero/pull/15)  
Where (which instance) does this need to be applied on?

---

<div class="post-metadata">

**Author:** ![megan.obrien](https://support.primero.org/forum/letter_avatar_proxy/v4/letter/m/7feea3/32.png) [@megan.obrien](https://support.primero.org/forum/u/megan.obrien)\
**Post date:** [June 2, 2021, 7:17pm UTC](https://support.primero.org/forum/t/gbvims-v1-5-incident-recorder-export-issue/438/6 "2021-06-02T19:17:55Z")

</div>

The IRC Uganda GBVIMS+ instance. Thank you!

---

<div class="post-metadata">

**Author:** ![irlawrence](https://support.primero.org/forum/user_avatar/support.primero.org/irlawrence/32/8_2.png) [@irlawrence](https://support.primero.org/forum/u/irlawrence)\
**Post date:** [June 11, 2021, 5:30pm UTC](https://support.primero.org/forum/t/gbvims-v1-5-incident-recorder-export-issue/438/7 "2021-06-11T17:30:04Z")

</div>

This fix has now been applied to that instance
