-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Namerequest UI: fix xpro (A company) mapping #18299
Comments
@severinbeauvais thank you for the update - is there anyway to get a report of the NRs that have been affected - hoping the volume is low |
The root cause is that we do a business search for the company to restore (or change, etc), which returns a business with Corp Type "A". This was incorrectly mapped to NR entity type "XUL". The correct mapping is "XCR". |
You should be able to search from them in Name Examination, applying the necessary filters. |
Oh, belay that... there is no filter for entity type "XUL". It will take an Ops report (db search) to get that info. @ozamani9gh ? |
@elizabethanneespinosa , are you able to help verify the fix in our Dev environment? https://dev.names.bcregistry.gov.bc.ca/ |
Would you like my team to submit a NR and see if it doesn't change type? |
Yes, please. In Dev. |
This fix has been tested locally, in Dev and in Test by various people including me, Kat, and Mihai. This fix is now in Prod. (I also verified it in Prod.) |
@severinbeauvais appreciate your quick response and fix on this one! |
This is the fix for Ops ticket 3229.
This will be a hotfix (no formal release) so I have linked it to the Namerequest WoN Release and will push this fix through by itself asap.
The text was updated successfully, but these errors were encountered: