How to do when ID always changes

If I remember correctly, it's not possible to use wildcards in XPath, but in normal name mappings you can.

Are you able to use any of the functions, https://www.tutorialspoint.com/xpath/xpath_string_functions.htm ?

You should ask that question to the developers of the application! The control could be dynamically generated. 

I also have something similar, on the application that I test, where the "id" is always changing. I have to use different properties to identify the object instead. I'm not using XPath, which makes things easier!

XPath example for the above control,

Question. Is it necessary for you to use XPath? Are you testing on Windows, macOS, Linux, Android and iOS?

If that's the case, then don't use XPath!

Have the following enabled/disabled (global settings)

Use Tree model (project settings),

Only map objects that you are interacting with, 

Click yes,

Skip mapped names (TC will automatically identify name and properties to be used), until you get to the last mapping i.e. 6/6

Provide a suitable name, and add any additional properties (it has to be unique)

Mapped objects and aliases (the name you provided) looks like this,

If textnodeHeading can not be highlighted, then the properties used in each of the objects in the tree structure has changed.

Identify the object,

and correct it, either using wildcards or full URL

This is how I build my mapped objects for the web application that I test. It might be long-winded, but it works great for a web application that was never indented or built for automation. Majority of all the objects don't have the "id" attribute in the web application that I test.

I disagree with this opinion ^^. Xpath is great thing and the most reliable (and faster) method to get any object on a web page. But, since TC only support Xpath 1.0 syntax, it requires some tricks to built it in the right way.

For exemple in this page (the TC forum page where we are) the button "Reply" has a part generated in its id. its look like this : 
//input[@id="submitContext_75b1b600eccb34_0"]

To get the button in the right way, We must identify the others components in the page and use some of them as "checkpoint" to be sure that we get the button always in the same way.

so the xpath become : //div[contains(@class, 'lia-inline-message-reply')]//div[contains(@class, 'lia-form-submit')]//input[@value='Reply']

in this way we get the reply panel, then the button group, and finally the reply button. As long as the architecture of the TC website (and/or css) doesn't change, this path is always the same.

namemapping is great too, but it can be pretty tricky to maintain when we have dozens of objects. Xpath is much more simpler.

For example,

This is checking the button property of Enabled, to see if it's equal to false.

Whereas, this is checking if the object exists,

Hi,

As per rraghvani, check if this work:

//div[starts-with(@id, 'grid')]//tr/td/i[contains(@class, 'c-grid-checkbox')]