try to use an import policy for that BGP neighbor instead of local-pref statement in the neighbor config.
set policy-options policy-statement XXX from protocol bgpset policy-options policy-statement XXX then local-preference 222set policy-options policy-statement XXX then accept
set protocols bgp group name neighbor YYYY import XXXset protocols bgp group name neighbor YYYY peer-as ZZZZ
It should solve your problem.
As Yasmin mentioned, Local Pref is purely for influencing *your AS* on how it routes out towards other neighboring AS's. So as she mentioned, Local Pref config on an I-BGP speaker feeds back into your local I-BGP domain, what it would like other local AS routers to do.
MED (multi-exit discriminator) would be how you would influence a remote AS on how you would like it to route back towards you, but, only if you are dual homed to the *same* remote ASYou will need to use other BGP knobs to accomplish your intended inbound influencing towards your dual homed / different remote AS's... like BGP path-prepending, or cutting prefixes into smaller pieces to have basic longest match ipv4 routing rule kick in.