https://community.blueprism.com/t5/Digital-Exchange/Not-able-to-change-value-from-drop-down-in-chrome-application/m-p/63103#M2491 Shikha,<BR /><BR />Have you identified the exact error with interacting with the drop-down element in your production environment?<BR /><BR />Typically, there are two things that could go wrong:<BR /> <OL> <LI>Blue Prism is not able to identify the drop-down element</LI> <LI>Blue Prism identifies the drop-down element, but is unable to make a selection on it</LI> </OL> <BR />In the first scenario, check the Attribute fingerprint for the drop-down element in your Application Modeller. It's possible that one of the attributes that need to be matched has a different value in Production versus the lower environments. For example if the URL attribute needs to be matched and the URL between UAT and Production is different, the element will fail to be identified.<BR /><BR /> <DIV class="media" style="overflow: hidden; zoom: 1;"><span class="lia-inline-image-display-wrapper" image-alt="8396.png"><img src="https://community.blueprism.com/t5/image/serverpage/image-id/8573i9C3BE53B2101822C/image-size/large?v=v2&amp;px=999" role="button" title="8396.png" alt="8396.png" /></span></DIV> <BR /><BR /><BR />In the second scenario, it may be worthwhile to determine whether there is a material difference in the drop-down element between Production and the lower environments. If the Attribute fingerprint is okay, and the drop-down still does not work in all environments, one should question what changed between environments. You might explore alternative ways of spying and interacting with the drop-down. I would suggest identifying it via the UI Automation Navigator and see if that behaves more consistently. As a last resort, you may be able to use a JavaScript injection to force a selection on the drop-down.<BR /><BR /><BR />------------------------------<BR />Charles Kovacs<BR />Developer Consultant<BR />Blue Prism<BR />America/Chicago<BR />------------------------------<BR /> Wed, 06 May 2020 16:40:00 GMT charliekovacs 2020-05-06T16:40:00Z https://community.blueprism.com/t5/Digital-Exchange/Not-able-to-change-value-from-drop-down-in-chrome-application/m-p/63102#M2490 Hello All,<BR /><BR />I need help. i am working blue prism&nbsp; version 6.4.3 and doing automation on chrome application.<BR />I&nbsp; have automated chrome application with browser mode but not able to change drop down value.<BR />i have already use select item with send keys but it is not working . it is working on lower environment like(Dev,Sit Uat).<BR />But production it is not working.<BR /><BR />please let me know if anyone can help me on the same.<BR /><BR />Thank you in advance...<BR /><BR />------------------------------<BR />Shikha Rahangdale<BR />Systems Engineer<BR />Infosys Ltd<BR />Asia/Kolkata<BR />------------------------------<BR /> Tue, 14 Apr 2020 06:21:00 GMT https://community.blueprism.com/t5/Digital-Exchange/Not-able-to-change-value-from-drop-down-in-chrome-application/m-p/63102#M2490 ShikhaRahangda1 2020-04-14T06:21:00Z https://community.blueprism.com/t5/Digital-Exchange/Not-able-to-change-value-from-drop-down-in-chrome-application/m-p/63103#M2491 Shikha,<BR /><BR />Have you identified the exact error with interacting with the drop-down element in your production environment?<BR /><BR />Typically, there are two things that could go wrong:<BR /> <OL> <LI>Blue Prism is not able to identify the drop-down element</LI> <LI>Blue Prism identifies the drop-down element, but is unable to make a selection on it</LI> </OL> <BR />In the first scenario, check the Attribute fingerprint for the drop-down element in your Application Modeller. It's possible that one of the attributes that need to be matched has a different value in Production versus the lower environments. For example if the URL attribute needs to be matched and the URL between UAT and Production is different, the element will fail to be identified.<BR /><BR /> <DIV class="media" style="overflow: hidden; zoom: 1;"><span class="lia-inline-image-display-wrapper" image-alt="8396.png"><img src="https://community.blueprism.com/t5/image/serverpage/image-id/8573i9C3BE53B2101822C/image-size/large?v=v2&amp;px=999" role="button" title="8396.png" alt="8396.png" /></span></DIV> <BR /><BR /><BR />In the second scenario, it may be worthwhile to determine whether there is a material difference in the drop-down element between Production and the lower environments. If the Attribute fingerprint is okay, and the drop-down still does not work in all environments, one should question what changed between environments. You might explore alternative ways of spying and interacting with the drop-down. I would suggest identifying it via the UI Automation Navigator and see if that behaves more consistently. As a last resort, you may be able to use a JavaScript injection to force a selection on the drop-down.<BR /><BR /><BR />------------------------------<BR />Charles Kovacs<BR />Developer Consultant<BR />Blue Prism<BR />America/Chicago<BR />------------------------------<BR /> Wed, 06 May 2020 16:40:00 GMT https://community.blueprism.com/t5/Digital-Exchange/Not-able-to-change-value-from-drop-down-in-chrome-application/m-p/63103#M2491 charliekovacs 2020-05-06T16:40:00Z