Boud Fields: ERROR: The Data Source has duplicate fields

Boud Fields: ERROR: The Data Source has duplicate fields

Posted by: rwhatley on 3 November 2018, 6:57 am EST

• 

  rwhatley

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 3 November 2018, 6:57 am EST

  I’m doing an evaluation regrading moving over from AR6 to AR12. Over the years we have developed a ton of reports so avoiding having to go through a significant conversion is essential.
  
  I modified our existing end user Report Designer. Using AR12 section reporting. It seemed to be working just fine. All our RPX files worked, the reports produced by AR6 and AR12 have so far come out identically. But, when working with the report data sources we use I encountered a significant issue. In * "AR6 "
  
  if I use a query like:

  SELECT c., s. FROM tblContract c, tblLinkContractStatus s WHERE c.ContractID = s.ContractID

  The bound fields all display.

  But, in AR12 the same query generates the error:

  ERROR: The Data Source has duplicate fields: ContractID

  Ok so why are we now seeing this error and is it possible to circumvent? I have noticed that if you drop a text box on the designer the “Data Field” drop down list all the columns correctly. I have also noticed existing reports still run even with this same error condition.

  • “This is no small issue.”
    
    because it undermines a lot of work already done and in circulation.

  For whatever reason it’s much simpler to join tables then having to identify just the columns used, at least for the non-technical users. I tried using the Query Tool provided but without the intelisense [sic] it’s not a very helpful tool. In addition the Query Tool Database view does not list table-valued function which we use.

  Any help will be appreciated

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 4 November 2018, 6:11 pm EST

  Hello,

  This behavior implements in the latest build of AR due to some internal cause. You can use the query builder to upgrade the query as per the latest version of AR. Please refer to the attached video to how to use the query designer. If still have any question, please let me know. I am more than happy to help you.

  Also, sorry for the inconvenience caused to you.

  Thanks

  vid_QueryDesigner.zip

• 

  rwhatley

  • Post Options:
  • Link
    Copy

  Posted 5 November 2018, 8:40 am EST

  Not sure I understand your reply. Is this a correctable issue in AR12, something you will fix in the future?

  Looked at the Query Designer, but it doesn’t offer much help in this matter. If you already have an existing query it comes up with the “Design” button disabled. So that makes it of no material help in fixing what we have in place. Also it doesn’t seem to reveal the table-valued function which is something we frequently use.

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 5 November 2018, 6:07 pm EST

  Hello,

  Sorry for the confusion, this behavior is implemented in the AR12 due to some internal cause which makes the current behavior “By-design”.

  We are understanding that this will be extra work for you, but you can change the query
  
  SELECT c., s. FROM Customers c, orders s WHERE c.CustomerID = s.CustomerID

  to
  
  select c.*, s.OrderID, s.CustomerID as [Order CustomerID], s.EmployeeID, s.Freight, s.OrderDate, s.RequiredDate, s.ShipAddress, s.ShipCity, s.ShipCountry, s.ShipName, s.ShippedDate, s.ShipPostalCode, s.ShipRegion, s.ShipVia
  
  from Customers c, Orders s Where s.CustomerID = c.CustomerID

  to make it work.

  If the above workaround is not acceptable to you, please let me know

  Thanks,

• 

  rwhatley

  • Post Options:
  • Link
    Copy

  Posted 7 November 2018, 5:41 am EST

  I always understood what changes were needed on my part. I don’t think I asked you how I could address this

  My question was related to what was happening and whether it was an error or something I had to live with.

  Sorry I wasted your and my time.

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 11 November 2018, 8:15 pm EST

  Hello,

  Apologies for the miscommunication.

  This was the issue in previous builds of AR where no error occurred even if the resultant query contained duplicate fields. This issue has been fixed in the latest build of AR hence you’re getting this error while upgrading the report from AR6 to AR12. From now onward, this will be a design behavior and hence, can’t be fixed.

  Hope it clarifies.

  Thanks,