How to avoid nested if condition?

I would try to extract a new private method or local function for comparing fields by names.

Assuming your example was in Java, I would aim for something like this:

    public void someBusinessLogicMethod() {
        // Define and intialize obj, objToFind, PropertyName
        // ...
        String[] fieldsToCompare = ["Name", "Role", "Value", "Class", "Top", "Left", "Height", "Width"];
        if (this.compareGivenFields(obj, objToFind, PropertyName, fieldsToCompare)) {
           // Some code.
        }
    }
    private Boolean compareGivenFields(Object obj, Object objToFind, Object PropertyName, String[] fieldNames) {
        Boolean result = false;
        for (String fieldName : fieldNames) {
            result &= compareField(obj, objToFind, PropertyName, fieldName);
        }
        return result;
    }
    private Boolean compareField(Object obj, Object objToFind, Object PropertyName, String fieldName) {
        try {
            Field attributeField = PropertyName.class.getField(fieldName);
            try {
                String attribute = attributeField.get(PropertyName).toString();
                return obj.Attributes[attribute].Equals(objToFind.Attributes[attribute]);
            } catch (IllegalAccessException e) {
                System.out.println("Error accessing field value.");
            }
        } catch(NoSuchFieldException e) {
            System.out.println("There's no such field.");
        }
        return false;
    }

In other languages which support direct field access by name (PHP, Javascript) solution might be even simpler.

By the way, you're right if you think that we created more code than we saved. Sometimes it's better to just leave things the way the are.

However, that is the solution for growing number of sub-ifs. You can easily put more fields to compare, but the nesting level won't change.

Thanks for reply.

Are you suggesting refection for this ifelse.

The reflection has own cost for performance.

Is it ok?

As with all things in programming you have to balance performance cost with with any benefit gained. But I'd say if you're not running this code in a loop, don't worry about the performance.

Would you favor me, why it would be bother when it runs from loop?

Here's analogy: you work on the 20th floor, but the dining room is on 3rd floor. It's fine to take a 2-minute elevator ride once a day on a lunch break. However, if the only coffee machine is also there, you will have to spend hours riding back and forth each time you commit your code.

Jokes aside, here are 2 stackoverflow threads, where you can get in-depth answer:

http://stackoverflow.com/questions/224232/what-is-the-cost-of-net-reflection

http://stackoverflow.com/questions/25458/how-costly-is-net-reflection