{{Quickfixn}} Issue sending requests to broker

[Robert Maidla]

Hello,

Thank you for the prompt response! You are correct, I am building my first FIX application and am testing various features. The broker I’m using is Exante and after asking for a data dictionary, they responded: "We haven't any DataDictionary. Here is our FIX specification: https://exante.eu/clientsarea/media/manuals/ExanteFIX1.13.1_8RSKmeg.pdf <https://exante.eu/clientsarea/media/manuals/ExanteFIX1.13.1_8RSKmeg.pdf>”. I apologise if the question is too trivial, but how exactly can I add the message types to the dictionary my app is using so that I would be able to use “custom” messages?

Looking forward to hearing from you!
Thank you in advance and best regards,
Robert
> On 18 May 2018, at 19:38, Grant Birchmeier <gbirchmeier at connamara.com> wrote:
> 
> It sounds like you are new to FIX in general (which is fine).  Let's see if I can clear up a misconception that I think you are having.
> 
> The engine is built to support the default "vanilla" FIX message dictionary.  This is the one defined in the FIX spec, but in reality, that is probably best treated as a suggestion.  In practice, every FIX counterparty customizes their dictionary.  Your broker is no exception -- UASQ is not a standard message type.
> 
> You need to update your FIX DataDictionary xml file to match your counterparty's expectations exactly.  They should have documentation that describes what messages they use and what fields are in each message.
> 
> 
> On Fri, May 18, 2018 at 4:04 AM, Robert Maidla <robertmaidla at gmail.com <mailto:robertmaidla at gmail.com>> wrote:
> Hello,
> 
> I am testing some features of FIX on the QuickFix/n demo application. Whilst everything is going smoothly, I am unable to send an “Account Summary Request” to the broker with a message type of “UASQ”. I have been in touch with the support team of the broker and they’ve got the following response for me:
> 
> [2018-05-08 08:11:17.813] 8=FIX.4.4|9=104|35=UASQ|34=2|49=IBJ8094_TRADE_UAT|52=20180508-08:11:22.164|56=EXANTE_TRADE_UAT|20020=08117717|20023=EUR|10=159|
> [2018-05-08 08:11:17.882] 8=FIX.4.4|9=116|35=3|34=3|49=IBJ8094_TRADE_UAT|52=20180508-08:11:22.239|56=EXANTE_TRADE_UAT|45=2|58=Invalid MsgType|372=UASR|373=11|10=050|
> [2018-05-08 08:11:17.884] 8=FIX.4.4|9=116|35=3|34=4|49=IBJ8094_TRADE_UAT|52=20180508-08:11:22.241|56=EXANTE_TRADE_UAT|45=3|58=Invalid MsgType|372=UASR|373=11|10=045|
> [2018-05-08 08:11:17.885] 8=FIX.4.4|9=116|35=3|34=5|49=IBJ8094_TRADE_UAT|52=20180508-08:11:22.242|56=EXANTE_TRADE_UAT|45=4|58=Invalid MsgType|372=UASR|373=11|10=048|
> 
> From here we can conclude that your soft doesn't understand MsgType = UASR and inform us about that.
> 
> 
> My question is - what is causing the request on my end and how can I work around that?
> 
> Thank you all in advance!
> Best regards,
> Robert
> 
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com <mailto:Quickfixn at lists.quickfixn.com>
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com <http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com>
> 
> 
> 
> 
> -- 
> Grant Birchmeier
> Connamara Systems, LLC
> Made-To-Measure Trading Solutions.
> Exactly what you need. No more. No less.
> http://connamara.com <http://connamara.com/>
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20180522/7325c55c/attachment.htm>