Error: Report has related reports linked by filters and the referenced filters could not be found

Hi Rutger,

it could be a bug, and there is only really one way we can investigate import/export bugs. Our developers will need to step through the code over here and see what's happening during the import.

So, could you please upload a full backup of your Yellowfin database to our FTP website (I have just made an account for you - you will receive an email containing your details, if you don't get it please also check your spam folder) and also we will need just the schema of your data source (no data, just the empty tables and columns).

Please let me know when you have uploaded them.

Also, I would say it is worth upgrading your 7.3 to the latest build because your current instance is 9 months old which means it is missing a lot of code-fixes, and you never know, if the upgrade fixes this problem then you won't have to go through the process of uploading the database dumps.

regards,

David

Hi Rutger,

just letting you know that I have successfully downloaded and restored your 2 Yellowfin MySQL databases and your PostgreSQL datamart DDL, so all that remains is for me to replicate your issue and then raise a defect, although I will have to do this tomorrow because I've just run out of time.

regards,

David

Hi Rutger,looks like there are 2 tables missing (sales_country_current, proc_seller_current) for the report "Price access products - one supplier

SELECT DISTINCT
   "supplier_relations_products"."reference_date",
   "supplier_relations_products"."speed",
   "supplier_relations_products"."term",
   AVG("supplier_relations_products"."mrc")
FROM "datamart"."sales_country_current"
LEFT OUTER JOIN "datamart"."supplier_relations_products"
ON (
   "sales_country_current"."country_id" = "supplier_relations_products"."country_id"
)
LEFT OUTER JOIN "datamart"."proc_seller_current"
ON (
   "supplier_relations_products"."seller_id" = "proc_seller_current"."seller_id"
)
WHERE (
   "supplier_relations_products"."speed" IS NOT NULL
   AND "supplier_relations_products"."term" = 12
   AND "proc_seller_current"."name" = E' - - select supplier - -'
)
GROUP BY 
   "supplier_relations_products"."speed",
   "supplier_relations_products"."reference_date",
   "supplier_relations_products"."term"

Are you able to send across a script so that I can add them to the datamart?

regards,

David

Hi Rutger,

thanks for the newscript. I ran it but it didn't resolve the issue with the report "Price access products - one supplier". Then I noticed that the schema in the script was called "ods" and didn't match with the schema of your other script, so I took the liberty of changing it to "datamart" but that still didn't resolve the issue. Then I noticed that the table names in the script were "proc_seller" and "sales_country" whereas that report is looking for "proc_seller_current" and "sales_country_current", so once again I took the liberty of changing the script by adding "_current" to those 2 table names.

But unfortunately that still didn't resolve the issue, the report still wouldn't run. Then I noticed in the console the following error:

YF:2017-10-23 10:55:42:ERROR (DBAction:doSelect) - Error occured selecting iVBORw0KGgoAAAANSUhEUgAAARUAAABNCAIAAAAHJmebAAAGkElEQVR4nO2dz2rcSBDG9R572XfINfsEYQ95hoVc8gR7WXzZB5jjPMGe9mLMMnYmTIJRgvEgmMGYMQXBwSSErCf4EpbEh96DjFD6n1rVLalb+n40QtF0VZdmuubTyF1RJswcHBxYXrXjbru4Edm8uS1u2LEA0BXZ0AEAkDC2/OlHfwBIl+H1B9dvIF2G159sLubrhvbL3yKbs2MBoCuG158yf7I//7W12X/IHxAhgfXn5MVypuPkxdIYwfxBXhqbbPgj0nFtt+qIix8AGgk8XWaz2ff7e7XNZjNjBHNBREI8bHc7+vpVFAV9/izynK6vxXJJl5fG6zd1xqv5I+2r+dP2NAEoCaw/7Pyp2O1ou6WioLMzynN69YqWS1osyDF/VJFB/oDuGJv+aPPH/fqNd9ZgsoTXn/3+9slvf9Xbfn9b5k/pUNrW9efqii4vabOh9Rr6AxIgvP7s97dqs+vPbkf392K3o2/fxHZLd3fi/Jw+fhSnp/TunTg5oYsLJ/3JFNQOAvkDwhFef2502PNnu6WybTZUFLRe09u3D+Lz8iUdH9PRkZP+aBMD+QO6I7z+MPKnKOjuThQFffkizs/p0yeR5/T+vVit6OpKLBa02bjqj/qS9vePJFD4CQR4RPH3n7MzqtqbN5Tn9Po1rVYPv3yOjujw0Kg/AAzI8F+32VzkOX348LA9PaXra7FaEZE4PqaLC3F4SOs11u+AGBl+/RvWj4J0GV5/AEiX4fUnrC0AfZK2/uDaDwxL2vqD2iEwLGnrT0K1Q9o/3YLUiUh/+qwd6p9o8yfCkBIioveu/7XbfYL8GSUR6U+ftUOmogZ1jY9qYgzGsErIxX9jdrmsiFW3lqgsZwrciehd61N/tFNQms3Sq/bgpQ4uU9w0Os+5lA8uJxKtJCZEXPrTW+2Qy8QyvarFJFaSaNSnu0lStM7ZwVsGQv74E9F712ftUPD8qTqb+pv0Rx1R69YneHdb0Ja49Ke32qGO8sfirfH6rdEnO3iXwACPiN67PmuHpKsaoZujpksyfSRN/aXJah+90X/jVZk9DGnfcl7ATkT602ftEKYLCELa04hdO+SZP5mCj7c+nYOwRKQ/DFusHwXDgu82APikrT9hbQFoy3T1B9d+wJ/p6g9qh4A/09WfrmuHcN9sCoxEf/qvHWq8v4z8mQIj+Yx91m6L54/FP3+Ipz+71w655AbyZwqMRH98aofE70/E88fi15/ca4f0Dq0LdupH6utuTEtytD5BbIzkg+lTf7SzWZsnluPqjqUniJbx6A+7dqjSH0btkPZgwPxBCkXOSD4en9qhSn8YtUPag6Hyp9pHFkXLePSHXTtU6Y/7c4fUCd1d/miHA5Ewkg/Gp3ao0p+2zx1Sbxio9w/Unm2v35A8MTMS/fGpHar0B88dAm2Z7ndbVTtU6Q+eOwTaMhL9Ydhi/SjwZ7r6A4A/09WfsLYurJ9lWZZhG3zb6admB/rDgXftl2XZo7lAC9uGvT8J/eHY8mqH1s+QP+Eb9Cc9eLVD7vpTUt8J29zddhEA26fWEPqTni2vdshdf0qCTF+tB0e3/qMHd6vaQn/Sg7d2Ozn9GXZ0R1voT3q2vNqhUn/q1OeEekSaLvZuLhNOotVM1Y7rGJXUxxSG4wlKVtCf9GDrT7ljn9/2HfWg6lPrX+vBP39MA2nH9XSlNYH+RGSrrRSStkKnPy61Q9I3pVYThDV/TN1c0kAdtFX+2GezJSqTH9N+4wlKB6E/6cGrHSp//9Rx/AJ2nEn95492XzI0+XEJz+WsoT/p2fJqh+r330rSyh97bphCVf00WrU6a+hPevBqh6RvSu33umj62aPt5pgGqoe2KWQ6Yo/K0qHtCapHoD/p2fJqh5Jbf1AyeBj2kKA/6cGrHep6/ZuWMaWQNhjoT3q2vPWjyelPEg36MxUGX+c/1u2Anyn0J4wtmCbQHw6o/QYl0B+OLZ4dBEqgPxy6fnZQnzjevwpym6utk2HvrbkA/eHYej47yBOfWaXaungLNY8ZfiJPoaiDixafZwcFGD3olEL++AD94diynx0kdP/Nr/TPes96B62JulX9SKNLThonqMmt/RRM0aqD2s0t5xID8UYWM6GeHaTNlrZHLLmnibz97GzMH9W5NiSGuWOEAwL9+cHWpf4n4LODguSP6tAy4Tzzx+RBlUSLrbRvMXeMcEDijSxmQj07aAT5wwjP3nk8+ZOohvRgy352UNf5oz2ivuqTPxbzCebP/1FNgj+dAcLEAAAAAElFTkSuQmCCAA==" alt="/1FNgj+dAcLEAAAAAElFTkSuQmCCAA==" /> 

whereas in the "supplier_relations_products" table the "seller_id" is bigInt: 

 

So I want to change the datatype of one of the above "seller_id" columns but do not want to do the wrong one, so could you please confirm whether it should be varchar or bigInt? Also, could you please confirm if the other modifications I did to your script were correct (changing the schema and table names), because ultimately I want to have my environment over here the same as yours. 

thanks, 
David
                

Hi Rutger,

thanks for the script, now all reports on the dashboard tab "Supplier Relations (New)" are executing without error.

But unfortunately during the process of trying to import the export file some more missing tables have come to light:

- So if you could send across a DDL script for those 2 tables (datamart.proc_api_portal_buyer & datamart.suppliers_portal_account_activated) then that would be great!

I feel we are getting very close now.

- Also, just to make sure I do the same steps as you, could you please confirm the following:

1) export the dashboard tab "Supplier Relations (New)" from the ACCP environment, making sure to include all dependencies excepting the data source.

2) import the export file created in step 1) into the PROD environment making sure to use the REPLACE option for all content items.

- And one final thing: please tell me which version and build of Yellowfin is in your PROD environment (I know ACCP is 7.3 20170103).

regards,

David

Hi David,

I forgot about those two (the related reports). Sorry for that. See attached file for the DDLs.

I can confirm that the export/import process is as you describe.

For PROD we have the same version and build:

System InformationApplication Version:7.3Build:20170103

Thanks again!

Hi Rutger,

thanks for the script, and this time everything is complete - my environment is correct!

But the thing is, firstly I exported the dashboard tab "Supplier Relations (New)" and all dependencies from ACCP and then imported it into PROD and there were no problems at all. Then I thought that was strange, so I'd better try the Yellowfin Export file ("Supplier Relations NEW 20171016_6.xml") that you originally attached here, then during the course of the import process I became aware that there were 5 extra reports that weren't in my ACCP environment, they were:

SQL details - In bundle

SQL details - In order

SQL details - Pending

SQL details - stage check

SQL details - stage negotiated

So I guessed that's why my first replication attempt was successful - somehow my ACCP env was different than yours and thus my own export file was different than yours. So anyway, I kept on going through the import process with your export file and then I came to the screen you were talking about:

and then I continued with the import process and it went successfully. Then I tried to run that report "Lead time to quote (working days) - one supplier" and it ran successfully.

So what I can tell you is that the message you saw during the import process, "Report has related reports linked by filters and the referenced filters could not be found." is not in fact an error, it is only a warning. And also, the warning itself is actually a bug because there was nothing wrong with the import process. And in fact, you won't be aware but in recent months the whole Yellowfin Export/Import functionality has been totally revamped and bugs like that have been ironed out.

In summary I would say to just ignore that warning message on the Import Summary screen, and whenever it is possible, you should upgrade to the latest 7.3 and you will see a whole new Import/Export functionality.

regards,

David

Hi Rutger,

that's great news, thanks for letting me know!

And in the future, should you stumble across any other bug, then we already have your environment set up over here so it should be quick and easy to replicate the issue.

thanks,

David