Parsing issue for service object names containing NEXT as keyword (Fortinet import)

LordRouter — Fri, 15 Jul 2022 12:29:00 GMT

After importing my Fortinet config, the service object named POWERNEXT was incomplete and I had to fix the protocol and port by myself.
I did some tests and found that the parsing process stopped when it found NEXT after an edit keyword. I've tried different keywords used in the xml but only the NEXT in a service object fails.
Here's an example :
config firewall service custom
edit "SET"
set tcp-portrange 995
next
edit "CONFIG"
set tcp-portrange 996
next
edit "END"
set tcp-portrange 997
next
edit "NEXT"
set tcp-portrange 998
next
edit "EDIT"
set tcp-portrange 999
next
end
After the import, I have to fix manually the settings for the "NEXT" service object. The 4 other services are good.

I'm using Expedition version 1.2.27 - not sure which other version is affected.

topic Parsing issue for service object names containing NEXT as keyword (Fortinet import) in Expedition Discussions

Parsing issue for service object names containing NEXT as keyword (Fortinet import)