SETFILTER w WildCards Not Working as Expected - dynamics-nav

I have been trying to get Setfilter with wildcards working properly but i don't know why it isnt.
SETFILTER(Description,'*#%1*',"Assembly Header"."No.");
The filter does not work and does not display anything, probably because NAV is not interpreting %1 well

Found a solution, it is always better to make use of STRSUBSTNO function for wild cards concatenation
So, it do works fine
SETFILTER(Description,STRSUBSTNO('*#%1*',"Assembly Header"."No.");
:)

because it's working the other way around:
SETFILTER(Description,'%1','#*' + FORMAT(Assembly Header"."No.") + '*');
so [at][star]{search term}[star]
In NAV 2013R2 it's actually gave you an error message for '*#'
Cheers!

The only solution working for me in NAV 2018 was that of azatoth:
'*#....' not working
'#*....' working

Related

UE4 Grenade deal damage

I have a grenade BP which the hero throws and wondering how you would set this up ..
I have tried and works fine but this way is caused by a sphere collision and checks what is inside the collision during detonation.
I tried without casting but this didn't work out very well for me, Is there something else I should be doing?
Please ignore the "get overlapping actors" class filter, I only done that as a test, i usually leave it blank.
ideally id like to try some sort on line trace when the bomb detonates so it can check if its a direct hit rather than triggering even when safe behind cover.
Any help is greatly appreciated, thank you!
Is there casting necessary? say I had 10 other different AI characters, id have to cast through them all right
I tried without casting but this didn't work out very well for me, Is there something else I should be doing?
Please ignore the "get overlapping actors"class filter, I only done that as a test, i usually leave it blank
I found out using a MultiSphereTraceByChannel works much better.

I cannot view components of an array

I'm using the following openCV variables:
std::vector<cv::DMatch> best_matches;
std::vector<cv::KeyPoint> tkeypoints[15];
When I press the "." and try to get the components of best_matches, for example best_matches[i].queryIdx then queryIdx appears correctly in the suggestion list.
However, when I try to get the components of tkeypoints, for example tkeypoints[i].angle, I don't see that on the suggestion list and I get an error if I try to run it like that.
Why I can't access the components in the second array?
tkeypoints
best_matches
Since is
std::vector<cv::KeyPoint> tkeypoints[15];
you should access it like:
tkeypoints[i][j].angle

What does the __default__ prefix mean in ng-inspector?

What exactly does the __default__ prefix mean in ng-inspector as shown below?
I am trying to access this value and I'm not quite sure how.
Thanks!
The extension certainly didn't add that prefix, if it shows up in ng-inspector, something else added that to your model.

SSRS - Adding "LIKE" filter criteria to report builder

I want to add a LIKE filters with wildcards in SSRS report builder. I tried this using contains clause present in filter data section of report builder. I tried both '*' and '%', but of them failed.
I tried
MyFieldName contains 2451 - this succeds
MyFieldName contains 24* - this fails
MyFieldName contains 24% - this fails
From below link I feel that this is an old problem with no solution till yet.
http://connect.microsoft.com/SQLServer/feedback/details/202792/ssrs-adding-like-filter-criteria-to-report-builder
What do you guys suggest?
Thanks
Ravi Gupta
You could use the InStr function
=IIF(InStr(Fields!MyFieldName.Value, "2451"),TRUE,FALSE)
In SSRS we can't use Like. Instead of which you can use Contains.
IIF((MyFieldName).ToString().Contains("RequiredString"),"True","False)
In the report builder in Visual studio there is a Like and it works. Use a * as wildcard in your search string
Answering my own question, Below function worked for me:
IF(FIND(MyFieldName, "24") = 1, TRUE, FALSE)
This is just a partial answer as this will work for cases like (blabla*), but its not for cases like (bla*bla, blabla*). So anyone having a better idea is most welcome.
Got idea to do this from Darren's comment above.
Thanks
Ravi Gupta
The Report Builder does not support the LIKE operator. You must use CONTAINS;
This is pretty late to the party, but I worked out a solution for parameter filters for my dataset.
Adding a filter to my dataset with
Expression:
=IIF(InStr(Fields!AccountName.Value, Parameters!paramAccountName.Value) OR Parameters!paramAccountName.Value = "*", TRUE, FALSE)
Type
Boolean
Operator
=
Value
true
The parameter are defaulted to "*" so the report looks like it grabs everything by default.
I just came across this old thread and I'm curious why you can't use the like keyword, since I've always used it.
Did you try something like this?
Where (AccountName like '%' + #paramAccountName + '%' or #paramAccountName ='')

Is there a way to identify bolded (<b></b>) with Celerity

I'm using celerity to do some screen scraping and have come across the need to identify text elements that are in bold. Celerity offers a strong method but does not offer a bold method. Has anyone figured out a clever way around this with Celerity or other tool. I tried using:
browser.html.gsub!(<b>,<strong>)
browser.html.gsub!(</b>,</strong>)
I though I could replace the bold elements with strong elements and then simply use celerity's strong method, but this didn't seem to work.
Thanks in advance for your help.
It seems strange that b is missing but you can try:
browser.elements_by_xpath('//b').each do |b|
puts "#{b} is a bold tag"
end

Resources