Find more posts tagged with
Sort by:
1 - 7 of
71
- Did you create the Attribute name yourself?
- Are there special characters in it?
- Does it start/end with a number?
- Are there spaces before/after the name?
Usually this happens because there is some kind of filter condition that is causing the attribute to be excluded somewhere earlier in the process. Another culprit can be the name of the attribute has been changed slightly (i.e., attribute names are case sensitive so even having one character different can cause this problem).
@varunm1 @Telcontar120
@Edin_Klapic
Thank you all for your answers. Something went wrong with the attribute name, I renamed it and it worked perfect.
I don't know if it is a general problem or it just happened for other reason, but when I had the error, the repository had the same name with one of the attributes.
Do you think that this is the reason that error appeared?
@Edin_Klapic
Thank you all for your answers. Something went wrong with the attribute name, I renamed it and it worked perfect.
I don't know if it is a general problem or it just happened for other reason, but when I had the error, the repository had the same name with one of the attributes.
Do you think that this is the reason that error appeared?
Happy to hear that you were able to solve it 

The attribute name and the repository same are unrelated, so no problem there.
However, there are several other things which may have caused the error.
Happy Mining,
Edin
@varunm1
@Edin_Klapic
I think that when I copied the name to use it into filter examples and set role it had more spaces becauses of the " " characters. So I don't think that there was something else that affected it.
Thank you both for your answers.
@Edin_Klapic
I think that when I copied the name to use it into filter examples and set role it had more spaces becauses of the " " characters. So I don't think that there was something else that affected it.
Thank you both for your answers.
Sort by:
1 - 1 of
11
@varunm1 @Telcontar120
@Edin_Klapic
Thank you all for your answers. Something went wrong with the attribute name, I renamed it and it worked perfect.
I don't know if it is a general problem or it just happened for other reason, but when I had the error, the repository had the same name with one of the attributes.
Do you think that this is the reason that error appeared?
@Edin_Klapic
Thank you all for your answers. Something went wrong with the attribute name, I renamed it and it worked perfect.
I don't know if it is a general problem or it just happened for other reason, but when I had the error, the repository had the same name with one of the attributes.
Do you think that this is the reason that error appeared?
Try to set breakpoint (Right-click on operator) on filter examples or set role operator (breakpoint before) and run the process to see if the attribute is coming into the operator, if not then you might look into the flow before this and see if that attribute is available or getting filtered out somewhere.