Hi Mike and Tammy,
1) Considering the original requirement, I think what you see below is expected. The formula/filtering that you applied here would be on the Column and not Rows, if I'm understanding this correctly. So, what the report shows now is, if there's a matching string1 it shows the string2 you want it to display, if it doesn't find a match it shows an empty cell.
Ref_Num | Summary | |
15663 | This is a sample ticket | Survey Sent and Received |
15663 | This is a sample ticket | |
2) Report showing OK data but export to CSV showing duplicates. Depending on the query though native report may issue only one main query to fetch data, for CSV BOXI may end up issuing separate queries against the d/b, and so, export to CSV could have duplicate records. This should not happen for all reports from what I know. SAP techs confirmed that the above behavior is a limitation of the way CSV exports work
3) If you are joining objects from two different classes (tables), a manual join would normally make it show unique records (of course matching the filter criteria). For example, if you want to pull some objects from incident detail and you want to display all act_log recordds. incident details --> ref_num, assignee_userid, status AND incident activity --> analyst_userid, last_mod. You then need to create a join forcibly between these two classes, by dragging incident details --> persistent_id Equal_TO incident activity --> call_req_id.
If this is not done, you may end up seeing a call_req record with all act_log records, and it repeats for each call_req record.
4) Assuming (3) was taken care of, if you still have duplicates then its probably because of uniqueness. Maybe certain criteria you're using is infact not unique and that's why the duplicate record shows up. I've seen some customers edit the query and manually the query to a custom query to have a left outer join or right outer join or what ever criteria that they really wanted there. That might be an option somehow?
_R