@rajesh-kumar said:
thank u its working
Glad to help.
i have same problem with another data
Then try a similar solution. Instead of searching for things inside of <cd>...</cd>, you’re looking for things that come after a prefix like "count": or "amount":. Even if you know nothing about regular expressions, you should be able to look at the regular expression I had defined before and have an attempt at it… it might not work right away, but you need to at least try. I’ll give you two more hints, because it’s buried a few links down in the regex documentation: the .* implies “any number of characters” in the regex, so you might want to use that when searching for any number of characters after your prefix. And the (?i-s) at the start of the regex is just making some settings to make it case insensitive, and to make sure that .* doesn’t wrap across lines. So using those two free gifts, you should be able to add in the permanent text that will look for one of your prefixes followed by any number of characters.
Note that based on your response – where you ignored the advice about how to format a post so that we can read the data, and to avoid getting real quotes translated into smart quotes; and a post where you ignore my advice of “many of us will expect you to show what data you have (exactly), what data you want (exactly), what regex you already tried (to show that you’re showing effort)” – it’s appearing like you want us to do your work and research for you, rather than learning; at this point, it seems you are treating this forum like a free-consultancy board, rather than a forum to help you learn how to use the tool yourself. Please correct that mis-understanding of this forum, or you’ll quickly grow disappointed.
Your first post got a free complete answer. For this one, I’m going to make you show effort (and I hope the other forum members do as well) before I give you any more complete answers. Before giving you any more explicit help, I will expect you to show that you’ve at least read the entirety of my first post – you can show this by re-posting your data, properly formatted; and by showing us what regex you tried (ie, a modified version of my original regex, showing that you’re looking for a prefix, followed by the rest of the line), what you think that regex should do, and show how your data didn’t change the way you expected when you ran your regex. This was all advice to you in the first post, which you apparently ignored. However, If you show even that much effort in your next reply – even if you haven’t availed yourself of reading the regex FAQ that was linked, and some of the pages linked in the FAQ – I’ll be willing to give more help.