https://community.blueprism.com/t5/Product-Forum/How-to-overcome-quot-more-than-one-matching-quot-error-to/m-p/55795#M10083 Maybe. If you can predict the attributes of the attributes of the elements that could appear, then you have a chance. Let's say there are 10 possible fields and they are called Field1, Field2....If you are able to add each filed to the application model, then you could use a wait stage to tell you if each one is present, either with CheckExist=False or through the timeout. But this all depends on the target application and whether the attributes of the elements follow a pattern. You need to be able to anticipate how the application will work Fri, 17 Nov 2017 19:10:00 GMT John__Carter 2017-11-17T19:10:00Z https://community.blueprism.com/t5/Product-Forum/How-to-overcome-quot-more-than-one-matching-quot-error-to/m-p/55792#M10080 Hello, In some part of the process, I need to give inputs to the boxes which I don't know how many of them will appear on screen. I tried to use wildcard matching for some attributes, and it worked for identifying; however the system gives "more than one matching" error. How could I proceed? Any help appreciated Fri, 17 Nov 2017 16:19:00 GMT https://community.blueprism.com/t5/Product-Forum/How-to-overcome-quot-more-than-one-matching-quot-error-to/m-p/55792#M10080 Ugur_KadirYıldı 2017-11-17T16:19:00Z https://community.blueprism.com/t5/Product-Forum/How-to-overcome-quot-more-than-one-matching-quot-error-to/m-p/55793#M10081 Ideally you need to find a combination of attributes unique to each element. Sometimes Ordinal can help, but not always. Physical coordinates/dimensions can be used, but the risk is they do not remain constant. Also research Match Index and Match Reverse. Fri, 17 Nov 2017 16:39:00 GMT https://community.blueprism.com/t5/Product-Forum/How-to-overcome-quot-more-than-one-matching-quot-error-to/m-p/55793#M10081 John__Carter 2017-11-17T16:39:00Z https://community.blueprism.com/t5/Product-Forum/How-to-overcome-quot-more-than-one-matching-quot-error-to/m-p/55794#M10082 Thanks John. The problem is not about differentiating fields. Actually the fields are differentiable but they could be any number and I could not how many fields there will be. Is there a way to identify them with some kind of logic? Thanks Fri, 17 Nov 2017 16:47:00 GMT https://community.blueprism.com/t5/Product-Forum/How-to-overcome-quot-more-than-one-matching-quot-error-to/m-p/55794#M10082 Ugur_KadirYıldı 2017-11-17T16:47:00Z https://community.blueprism.com/t5/Product-Forum/How-to-overcome-quot-more-than-one-matching-quot-error-to/m-p/55795#M10083 Maybe. If you can predict the attributes of the attributes of the elements that could appear, then you have a chance. Let's say there are 10 possible fields and they are called Field1, Field2....If you are able to add each filed to the application model, then you could use a wait stage to tell you if each one is present, either with CheckExist=False or through the timeout. But this all depends on the target application and whether the attributes of the elements follow a pattern. You need to be able to anticipate how the application will work Fri, 17 Nov 2017 19:10:00 GMT https://community.blueprism.com/t5/Product-Forum/How-to-overcome-quot-more-than-one-matching-quot-error-to/m-p/55795#M10083 John__Carter 2017-11-17T19:10:00Z