Problems with Version 7?

I have now given up trying to get a complete statement on V7 so am trying to revert to V6 where the statement problems do not exist.
However despite saving the V7 TRIGGER block as an XML file, i cannot open the xml triggers in V6. All the original XML triggers which were written in V6 not V7 open normally.
Any suggestions as the trigger block remains blank despite everything i have tried.
THX GUYS

I don't believe the triggers are backwards compatible, so after writing in V7 they won't work in v6.  Perhaps support would be able to convert them for you?

I have now given up trying to get a complete statement on V7

BF Winner, may I get more information on this: do you mean you are not getting all the P/L in real time as your bets get settled, or do you mean you cannot open and browse your statement?

BF Winner, may I get more information on this: do you mean you are not getting all the P/L in real time as your bets get settled, or do you mean you cannot open and browse your statement?

Hi Oxa
This is the same problem that I referred to about 3 months ago. The problem is the platform continues to crash randomly every day, but remains open, so unless I remember to restart the platforms regularly (all 3 are effected on two PCS) no statements are downloaded. Hundreds of test bets are made and clearly visible, but only partial or often no statements are available to view.
I believe the problem is the "once per selection" criteria putting a heavy strain on the bots, but even splitting the triggers into 3 different platforms has made little difference.
i remained on V7 in test as the results include reduction factors but V6 does not; otherwise i would have reverted to V6 3 months ago rather than persevering with V7 as there is no problem getting the statements in V6.
Each incidence has 10 triggers set with "once per selection" making 30 triggers on the 3 seperate accounts. 

Hi Oxa / Tim
Small error in Distribute Loss action:
If you select based on profit %, the manual states that parameter “Loss %” appears. In fact parameter
“Profit %” appears, which can be somewhat confusing.

Am having problems viewing log files.
Clicking statement or program logs brings up same result screen - red bar at the top saying "undefined".
I pressed the save icon and was met with a funny reply "Error Damn!"
See screen shots attached.

Been working fine until todays trading effort.
Uninstalled and re-installed...gave MF7 full access past firewall...no joy!

Possible clue ... my trigger was MISTAKENLY (my mistake!) firing a lay bet in TEST mode every 3 secs ending with several hundred which activated the bets summation in the my bets section.
I clicked the statement icon to review the logs to find the reason for the 100+ bets per market and got the screen shots described/attached.

How can I get to see my logs as MF7 developers intended?

While I'm on this issue...it would be great if it was possible to review log files without starting MF7/logging into BetFair...like the trigger editor. I know you can manually unzip the log files and use your browser to view the resulting text file but this is very laborious trying to review numerous logs to find out why what happened happened.

OT

Hi all

Any of you have a clue about this error???

thanks

Am having problems viewing log files.
Clicking statement or program logs brings up same result screen - red bar at the top saying "undefined".
I pressed the save icon and was met with a funny reply "Error Damn!"
See screen shots attached.

Been working fine until todays trading effort.
Uninstalled and re-installed...gave MF7 full access past firewall...no joy!

How can I get to see my logs as MF7 developers intended?

Finally discovered the reason why the log viewer stopped working.
The log viewer links (program/statement/triggers) will show nothing if ANY trigger has the character "&" in the name.
Had a trigger named "T & J" ... log viewer showed "undefined".
Renamed it "T and J" ... log viewer worked fine! 

Finally discovered the reason why the log viewer stopped working.
The log viewer links (program/statement/triggers) will show nothing if ANY trigger has the character "&" in the name.
Had a trigger named "T & J" ... log viewer showed "undefined".
Renamed it "T and J" ... log viewer worked fine! 

Thanks very much for posting this information. I don't think this is documented in the manual with regard to acceptable characters for trigger names, and it may resolve some issues one or two other people have had.

I agree Mark .. Thanks Obias

Hi
If I am using the editor while a market is refreshing, and that market finishes and is deleted, the attached error is displayed and the getting started screen does not appear.

I think I got this once. Re installing it fixes everything. I hope it does the same for you.