Sure, I took this ticket.
I used your private details submitted here to access the backend you link.
https://toolset.com/forums/topic/need-a-result-displayed-as-a-link/#post-1190948
Let me reply to your questions:
1. i cant begin to type the name to choose the sire or dam ,that list will soon be 1000-2000 entries.
You are using a Select Field, that Select Field is populated in Toolset > Custom Fields > Field Group for Dogs > Dog Sire/Dogs Dam
When editing a post you will not be able to add values to it, only to choose values, and there will not be a Select2 instance that lets you type and search thru thousands of options but only a simple select field that will react to the first keystroke (Press F to get first letter of F, for example)
To achieve a field where you type and search you cannot use one of Toolset's Custom Fields as there is no such field.
I suggest to submit a request for a Select2 instance Field in Types here:
https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/
Meanwhile, though you could use a post Relationship (this is the only way to have such a Select2 Field).
Hence you would rather connect Posts that determine the Dog Sire and Dam values.
Or, you would have to choose other plugins that allow such fields (I believe ACF has).
2. Yes, to do so you need to apply the exact HTML conditional as I outlined, adapted to your case.
However I cannot see where you style that post as there is no Content Template for it and it has no content in the post body either.
In the template where you add the HTML and ShortCodes to display the data, there wrap the Sire (and any other fields you want to check for empty/not empty) in the Conditional.
There is a button for that in the TinyMCE Editors, called conditional, as the documentation outlines.
When you use this you can insert such conditions manually with ease.
If you indicate me the place where you style those posts I can insert an example code.
3. Waqar's code is unrelated to the front end, it is a code that populate a custom select field with wpt_field_options.
Do you know that fields, registered with wpt_field_options, are not usable in Toolset View's Custom Searches without lots of add-on Custom Code?
If this is within the planned amount of time and work you intend to invest this is fine, however I have to warn you ahead that such fields cannot be used easily in Custom View Searches. This is a known issue, which we intend to solve in future, but I have no ETA for this at all, unfortunately.
Now, this code does manage the field in the backend, it populates it with posts.
I also wanted to inform you about post reference fields, as it seems to me you could profit from this:
https://toolset.com/documentation/post-relationships/how-to-display-related-posts-with-toolset/using-post-reference-fields-to-display-information-from-a-related-post/
It seems to me this is exactly what you need to populate the dog sire and dam fields, but I might be totally wrong as I am not yet 100% familiar with the setup and initial goal.
In any case, the field you have now, can be hidden in the front end if empty, with the suggested HTML condition, but I cannot find the template to do an example code.