# In RDD, adding Criteria to UD Table returns "The field is no valid" error **URL:** \ **Category:** Kinetic ERP\ **Tags:** ud-field-rdd, ssrs\ **Created:** [August 1, 2023, 6:56pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632 "2023-08-01T18:56:06Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![Andrew](https://www.epiusers.help/letter_avatar_proxy/v4/letter/a/f19dbf/32.png) [@Andrew](https://www.epiusers.help/u/Andrew)\ **Post date:** [August 1, 2023, 6:56pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/1 "2023-08-01T18:56:06Z")
Hello All. I’m hoping someone has found a way around an apparent limitation in Report Data Definition when adding a UD table AND criteria against that table. I’ve added UD03 and a relationship to the Part table (Part.Company = UD03.Company). Obviously, a very wide open join. Now it gets interesting as I have to use criteria on the UD03 table to limit what is returned. I’m adding the following criteria to the UD03 table in order to specify the records I want returned. ![image](https://www.epiusers.help/uploads/default/original/3X/6/3/6324b7e9ddfb65aa59bff3f53f85b3ffc274ef5f.png) Translation: `UD03.SI_color_code_c = Part.SI_Color_Side_1_c` So this equation has UD fields on both sides and generates the following error: ![image](https://www.epiusers.help/uploads/default/original/3X/8/f/8f1cd4baa00da16bb011e9cfbecb0aaba5a32081.png) This error appears to be related SOLELY to the right side of the equation. If I change change the `Part.SI_Color_Side_1_c` to `Part.PartNum` (and ICE to ERP), there is no error. Now, you might ask, why not just specify that criteria in the RDD’s relationship record. I’m glad you asked… The above criteria will be a “This **OR** that” criteria - which I cannot accomplish in an RDD relationship. So I have to figure out how to limit what’s returned from that UD table via the table criteria. Any thoughts will be greatly appreciated. ---
**Author:** ![HLalumiere](https://www.epiusers.help/letter_avatar_proxy/v4/letter/h/bc8723/32.png) [@HLalumiere](https://www.epiusers.help/u/HLalumiere)\ **Post date:** [August 1, 2023, 6:58pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/2 "2023-08-01T18:58:48Z")
Did you include (uncheck Exclude) the fields you want to use in the criteria? ---
**Author:** ![Andrew](https://www.epiusers.help/letter_avatar_proxy/v4/letter/a/f19dbf/32.png) [@Andrew](https://www.epiusers.help/u/Andrew)\ **Post date:** [August 1, 2023, 6:59pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/3 "2023-08-01T18:59:20Z")
Thanks Hugo. I sure did. In fact, as i mentioned, if I specify this relationship AS a relationship, no problem!!! It’s just when I use it in the Table Criteria where I get an error. It seems not to like a UD field to the right of the equal sign. ---
**Author:** ![kve](https://www.epiusers.help/user_avatar/www.epiusers.help/kve/32/76150_2.png) [@kve](https://www.epiusers.help/u/kve)\ **Post date:** [August 1, 2023, 7:43pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/4 "2023-08-01T19:43:59Z")
> [@Andrew](#): > > `Part.SI_Color_Side_1_c` to `Part.PartNum` (and ICE to ERP), Are UD Fields on ERP Tables using the ICE System code? I’m not on Kinetic yet, but I’ve never seen these used with ICE. Please disregard if that’s a change in Kinetic that I’m not aware of. ---
**Author:** ![Andrew](https://www.epiusers.help/letter_avatar_proxy/v4/letter/a/f19dbf/32.png) [@Andrew](https://www.epiusers.help/u/Andrew)\ **Post date:** [August 1, 2023, 8:01pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/5 "2023-08-01T20:01:35Z")
I believe so @kve . Regardless of selection (ICE/ERP) I receive an error with a UD field on the right side of the equal sign, However, if I specify Part.PartNum, I MUST select ERP, otherwise I receive an error (the SAME error). ---
**Author:** ![klincecum](https://www.epiusers.help/user_avatar/www.epiusers.help/klincecum/32/100137_2.png) [@klincecum](https://www.epiusers.help/u/klincecum)\ **Post date:** [August 1, 2023, 8:36pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/6 "2023-08-01T20:36:31Z")
Step back a step. I’d like an answer too, but what is this report, can you do this in a BAQ instead? Might be a workaround if this can’t be accomplished. ---
**Author:** ![Andrew](https://www.epiusers.help/letter_avatar_proxy/v4/letter/a/f19dbf/32.png) [@Andrew](https://www.epiusers.help/u/Andrew)\ **Post date:** [August 1, 2023, 8:41pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/7 "2023-08-01T20:41:22Z")
Thanks @klincecum , I may very well have to create a BAQ report, BUT this is a duplicate of the Job Traveler. There’s a lot of ‘good stuff’ in there I’d like not to have to build from scratch, so I’m using the (copied) RDD, and simply adding a UD table. It’s not a difficult thing to do, unless the join is complicated, which this one is, hence I have to ‘finesse’ the where clause in the Table Criteria. ---
**Author:** ![klincecum](https://www.epiusers.help/user_avatar/www.epiusers.help/klincecum/32/100137_2.png) [@klincecum](https://www.epiusers.help/u/klincecum)\ **Post date:** [August 1, 2023, 8:53pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/8 "2023-08-01T20:53:25Z")
_Shot in the dark._ Add the UD table, AND it’s associated UD Fields table, and link those together, then use the ud fields table as the criteria. IE, UD03 and UD03\_UD, (I forget how they are linked), and then use the UD03\_UD.yourfield or in your case maybe the Part\_UD table linked to Part and use Part\_UD.yourfield You shouldn’t normally have to do any of that, but maybe it’ll work ? 🤔 ---
**Author:** ![klincecum](https://www.epiusers.help/user_avatar/www.epiusers.help/klincecum/32/100137_2.png) [@klincecum](https://www.epiusers.help/u/klincecum)\ **Post date:** [August 1, 2023, 8:57pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/9 "2023-08-01T20:57:48Z")
Link them on Part.SysRowID and Part\_UD.ForeignSysRowID ---
**Author:** ![Andrew](https://www.epiusers.help/letter_avatar_proxy/v4/letter/a/f19dbf/32.png) [@Andrew](https://www.epiusers.help/u/Andrew)\ **Post date:** [August 1, 2023, 8:58pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/10 "2023-08-01T20:58:59Z")
It’s a good thought. I tried adding Part\_UD but the relationship kept failing. It seems like the RDD doesn’t like the “\_UD” tables. Again, its a pretty standard add (SysRowId = ForeignSysRowId), but RDD keeps complaining that it can’t find the field ForeignSysRowID. I could try the other side of the equation (the UD03 table to UD03\_UD), but its essentially the same as what I tried. It seems like, since the UD fields ARE available (without adding the “\_UD” tables), adding them generates the error Can’t find the field ‘ForeignSysRowID’. ---
**Author:** ![klincecum](https://www.epiusers.help/user_avatar/www.epiusers.help/klincecum/32/100137_2.png) [@klincecum](https://www.epiusers.help/u/klincecum)\ **Post date:** [August 1, 2023, 9:01pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/11 "2023-08-01T21:01:20Z")
> [@Andrew](#): > > but RDD keeps complaining that it can’t find the field ForeignSysRowID. I’ve found that after you remove the exclusions and save, sometimes you need to refresh the screen before you can get the relationships section to work properly. I just set it up in mine, and that’s what I had to do. ---
**Author:** ![Andrew](https://www.epiusers.help/letter_avatar_proxy/v4/letter/a/f19dbf/32.png) [@Andrew](https://www.epiusers.help/u/Andrew)\ **Post date:** [August 1, 2023, 9:02pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/12 "2023-08-01T21:02:06Z")
And you were able to add Part\_UD ?? ---
**Author:** ![klincecum](https://www.epiusers.help/user_avatar/www.epiusers.help/klincecum/32/100137_2.png) [@klincecum](https://www.epiusers.help/u/klincecum)\ **Post date:** [August 1, 2023, 9:02pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/13 "2023-08-01T21:02:14Z")
Yes ---
**Author:** ![Andrew](https://www.epiusers.help/letter_avatar_proxy/v4/letter/a/f19dbf/32.png) [@Andrew](https://www.epiusers.help/u/Andrew)\ **Post date:** [August 1, 2023, 9:03pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/14 "2023-08-01T21:03:22Z")
Hmm… I know I’ve gone far down this rabbit hole, but let me investigate further. ---
**Author:** ![DaveOlender](https://www.epiusers.help/user_avatar/www.epiusers.help/daveolender/32/260_2.png) [@DaveOlender](https://www.epiusers.help/u/DaveOlender)\ **Post date:** [August 1, 2023, 9:16pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/15 "2023-08-01T21:16:34Z")
Could you consider running the report Without the UD Criteria? Then apply the UD Color join in the SSRS Select Query? DaveO ---
**Author:** ![Andrew](https://www.epiusers.help/letter_avatar_proxy/v4/letter/a/f19dbf/32.png) [@Andrew](https://www.epiusers.help/u/Andrew)\ **Post date:** [August 1, 2023, 9:19pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/16 "2023-08-01T21:19:35Z")
Hi @DaveOlender . In fact, that’s exactly what i am doing in order to test the usability of the report. It’s slow, however, as its pulling down about 5K rows from that UD table - instead of 2!!! ---
**Author:** ![Andrew](https://www.epiusers.help/letter_avatar_proxy/v4/letter/a/f19dbf/32.png) [@Andrew](https://www.epiusers.help/u/Andrew)\ **Post date:** [August 1, 2023, 11:13pm UTC](https://www.epiusers.help/t/in-rdd-adding-criteria-to-ud-table-returns-the-field-is-no-valid-error/105632/17 "2023-08-01T23:13:11Z")
@klincecum, I added the UD03\_UD and the Part\_UD to the RDD. I established relationships between these by SysRowID = ForeignSysRowID as you outlined. I then selected the UD03 table and created the Table Criteria to limit the returned rows. No problem with these (Yay!) Attempting to preview the report, however, reveals the errors. In System Monitor, under History/Logs - unable to bind the UD fields, and no report is produced. ![image](https://www.epiusers.help/uploads/default/original/3X/b/7/b7c9101ab6dd4695215a92b411acc77ddb31daac.png) So incredibly frustrating!