I'm trying to delete a passenger from PNR using Sabre web services
What I did is the following
Create PNR (1 flight segment 2 passengers)
GetReservation
TravelItineraryModifyInfoRQ (delete passenger)
EndTransaction
EndTransaction shows an error NUMBER OF NAMES NOT EQUAL TO RESERVATIONS
Create PNR (1 flight segment 2 passengers)
GetReservation
TravelItineraryModifyInfoRQ (delete passenger)
OTA_CancelRQ (cancel flight)
Book the same flight, but for 1 passenger
EndTransaction
EndTransaction shows an error TO REDUCE NUMBER IN PARTY ENTER COMMA FOLLOWED BY NEW NUMBER
As I understand the error says how to delete passenger using Sabre interact, not web services
This works for me :
GetReservation
TravelItineraryModifyInfoRQ (delete passenger)
HostCommand ",{new number in party}"
EndTransaction
Related
I am querying my graph where it has the following nodes:
Customer
Account
Fund
Stock
With the following relationships:
HAS (a customer HAS an account)
PURCHASED (an account PURCHASES a fund or stock)
HOLDS (a fund HOLDS a stock)
The query I am trying to achieve is returning all Customers that have accounts that hold Microsoft through a fund. The following is my query:
MATCH (c:Customer)-[h:HAS]->(a:Account)-[p:PURCHASED]-(f:Fund)-[holds:HOLDS]->(s:Stock {ticker: 'MSFT'})
WHERE exists((f)-[:HOLDS]->(s:Stock))
AND exists ((f:Fund)-[holds]->(s:Stock))
AND NOT exists((a:Account {account_type: 'Individual'})-[p:PURCHASED]->(s:Stock))
RETURN *
This almost gets me the desired results but I keep getting 2 relationships out of the Microsoft stock that is tied to an Individual account where I do not want those included.
Any help would be greatly appreciated!
Result:
Desired Result:
There is duplications in your query. Lines 2 and 3 are the same. Line 2 is a subgraph of Line 1. Then you are using the variables a, p and s more than once in line 1 and line 4. Below query is not tested but give it a try. Please tell me if it works for you or not.
MATCH (c:Customer)-[h:HAS]->(a:Account)-[p:PURCHASED]-(f:Fund)-[holds:HOLDS]->(s:Stock {ticker: 'MSFT'})
WHERE NOT exists((:Account{account_type: 'Individual'})-[:PURCHASED]->(:Stock))
RETURN *
It seems to me that you should just uncheck the "Connect result nodes" option in the Neo4j Browser:
In GA4, I am using a custom event to send AB Tests metadata from my Adobe Target experiences.
The code is as follows:
window.gtag('event', 'ab_test', {
'test_name':'${campaign.name}',
'test_id':'${campaign.id}',
'variation_name':'${campaign.recipe.name}',
'variation_id':'${campaign.recipe.id}',
})
Checking the network requests and the Debug View I know that the data is properly sent (and received).
In the Explore reporting feature I have created a Free from report with my AB Test Variation Name as a dimension, AB Test Name as a column, and Conversions, Transactions, Purchase Revenue as metrics.
Furthermore, I have created 2 segments, one identifying visitors having an ab_test event count > 0 and the other < 0. This segment is created at a User scope. (also tried at a session scope). But in any case, all the metrics always end up empty.
My expectation is obviously that I could correlate the exposure to an AB Test to sales and other conversion metrics.
Any idea why the data isn't showing up?
In my SpringBoot Application using Prometheus, I created a metric type Count that brings me the following information :-
pre_analise_executadas_total{id_partner="parceiro1",id_person="pessoa2",id_product="produto1",id_proposal="proposta3", id_employee="operador1",} 1.0
For each new proposal generated, prometheus presents me with this information and assigns a value of 1 to the counter, because in this combination of attributes each proposal will be unique.
How can I generate a graph in Grafana that shows the variation in the number of proposals contracted per employee each day of the month?
I'm currently retrieving a PNR information using the Retrieve PNR API. For display, i need to group the flights by legs. However, the flight returned in the view i'm using (DefaultWithPq) are simply returned as a single sequence of segments :
<stl18:Segments>
<stl18:Segment sequence="1" id="8">
...
<stl18:Segment sequence="2" id="9">
...
<stl18:Segment sequence="3" id="10">
...
<stl18:Segment sequence="4" id="11">
...
</stl18:Segments>
How is it possible from those sequence (without calculating with departure times destinations etc.) to know which ones are in the departure leg and which ones are in the return leg ?
thank you
Unfortunately this would be have to be done by your application's logic, as the service does not return that information. You can use dates and marriage indicators but there is no element to show which one is the inbound or outbound flight. Usually customers obtain this with shopping services like BFM.
I would like to know how to pass Frequent Flyer's number in case 2 different Airlines.
Do I need to pass Airline wise i.e Segment wise, or can I pass for Marketing Airline.
For Instance:
Say Marketing Airline is "9W" and Suppose 2 connecting Airlines are "9W" and "AI", so in this case, will it be ok if I just pass for "9W" (Marketing Airline) ?
I think passing MarketingAirline in ProgramID should be OK.
according to Sabre documentation, you can pass frequent flyer number using PassengerDetailsRQ when creating PNR with this XML element:
<CustLoyalty MembershipID="155P9B76" NameNumber="1.1" ProgramID="XX"
SegmentNumber="1" TravelingCarrierCode="YY"/>
The thing you have to know that you can't combine SegmentNumber element with TravellingCarrierCode. In your case, you have two different airlines to ticket but you want pass the frequent flyer number to only one of these, then you can do:
<CustLoyalty MembershipID="155P9B76" NameNumber="1.1" ProgramID="XX" TravelingCarrierCode="XX"/>
ProgramID is the airline that you want to pass the frequent flyer number, TravellingCarrierCode can be same or different (due to operating / marketing airline differentiation). NameNumber stands for passenger I guess, I didn't have exact information for that so I don't want to give you wrong information about that attribute.
The schema you should follow in request is:
PassengerDetailsRQ --> TravelItineraryAddInfoRQ --> CustomerInfo --> CustLoyalty
Regards.