Max no of Qualified links

Hi,
Is there any limit of maximum number of qualified links that a field of type Lookup[Qualified Flat] (multi-valued) can contain.
Regards,
Sandeep Reddy.

Hello Sandeep
To have a better performance, you may follow the suggestions below:
non-qualifier:
Green: < 10 000
Yellow: 10 000 u2013 100 000
Red: > 100 000
qualified links:
Green: < 1M
Yellow: 1M - 10M
Red: > 10M
Best regards,
Dale

Similar Messages

Filter Qualified Link Checkbox set for tuples, But syndicated all Recs

Hello MDM Gurus,
With Reference to the answer below.. we have tuples and we are doing the same, but still we are getting all three links in the syndicated file.
I have tested this using flat syndication file.
Original Thread
Hello all!
Here is an issue we are working on. We would like to syndicate entries from a qualified lookup table for a particular customer, but only those where a certain qualifier has a specific value. For example:
Qual Table:
Non-Qual1; Non-Qual2; Qualifier.
Entries:
"AA", "123", "Yes"
"BB", "123", "No"
"CC", "456", "Yes"
So, when I syndicate this customer record, I would only like to syndicate those entries where the Qualifer = "Yes".
"Supress Unchanged Records" only works on the whole customer record and if the Search Criteria is set for "Qualifer = "YES", then it chooses the record (correctly), but syndicates all entries from the table.
Answer
Try using
Filter Qualified Links in the Map Properties of the Syndicator.
If activated, syndication results contain only the data selected in the Selection Pane.
Tick the check box under the Value Column for that property. By default that check box is not selected. You have to check it.
This works similar to the 'Filter' check box of the MDM Data Manger.
Limitation as of SP04
- One Global setting per map for qualified links plus one global setting per map for multi-valued lookups.
Please help us to resolve this issue. your input will be highly appreciated.
Thanks in Advance.

I need to synidate all customer records regardless of contacts linked to the customer.
A customer can have one to many contacts. There are several contact functions such as Primary, Sold To, Owner, etc.
When I syndicate the customer, I need to syndicate all Customer main table data and include Contact data only if the Contacts function = Primary, otherwise the contact data should be null in the syndiation.
A customer may have no contacts --> Syndicate Customer main table data, contact data is null
A customer may have theee contacts: 1 = primary, 2 = ship to, 3 = owner --> Syndicate Customer main table data and Primary contact data
A customer may have two contacts: 1 = ship to, 2 = owner --> Syndicate Customer main table data, contact data is null (since no Primary contact exists)
I hope this clarifies the requirement.
thanks
Tammi

Looking for ideas: mass-delete qualified links

Hello SDNers!
I'm looking for an innovative idea on how to mass-delete qualified links. I want to delete all the qualified links to a specific non-qualifier from many records at once. Idealy the scenario would be to search on a specific qualifier, and be able to select all records and delete that qualified value from them. Data Manager can't do this, obviously.
The closest I managed to get was to delete all the values in the qualified link using an import, but that's not enough, I need to delete the links completely.
Before I turn to the APIs, anyone has an idea?
Thanks
Alon

Alon,
You should be able to accomplish this with an export and import.
1. Select the qualified record you want to delete using the search parameters
2. Export out the records with this qualified field - it should only export out the qualified record that you have selected in your search parameter
3. Import this file with the Import Manager
4. Map the qualified table name in the source to the destination
5. Right click on the destination field name and select "Select Qualified Update > Update"
6. A new dialog box will appear
7. For new links select "Skip"
8. For existing links scroll down and select "Delete"
9. When the file imports it should delete all instances of that qualified record
That was a quick explanation. Let me know if you need more detail.
Regards,
Tim

Qualified links to Relative links

Hi All-
I have created a course with links to pdfs in two if the
scos. They work fine when tested on my computer but when tested in
the LMS the pdfs won't come up: I need to change it from being a
fully qualified link to my hard drive, to being a relative link
pointing to the file in my course folder (in this case, it would
need to be ../Power_Handle_Training1a.pdf as the PDF exists in the
root of the overall course folder). I am not sure how to do this.
Please help.
Many thanks,
Rita

Simply set your button to open url or file and put the name
of the file in the box without any other info for ex.
Power_Handle_Training1a.pdf .
then make sure that everything including a copy of the pdf is
in the same floder after you publish. this should do it.

Nvarchar(max) of sql server 2005 is not accessible through Oracle DB Link

hi,
i have created the DB LINK from Oralce 11gR2 to MS Sql Server 2005,
am able to access the view of Sql Server from Oralce,
but the Columns which have Datatype nvarchar(max) in Sql Server am not able to access through DB Link.
can anybody know about this issues?

Pl do not post duplicate threads - Datatype nvarchar(max) not accessable (DB Link from Sql 2005 to Ora 11gR2 )

Not able to see data in the qualifier table of the main tbl , Data Manager

Hi,
I have an issue of not able to see the data of two qualified table after populating them.
It is in mdm-5.5 ps4.
When populating data first time ,it shows up in those two table slots in the right side of the Data Manager.
However subsequently it does not show up in those slots , only by right click on the table and selecting "View/edit", the window pops up where those data shows up.
However unlike other qualified tables the data does not showup automatically for these two tables.
Appreciate any suggestion or feedback on this.
regards,
-reo

You may have checked the Filter Check Box next to the Qualified Lookup cell in Data Manager, when the current table is the Main Table.
You use the Filter Checkbox to limit the qualified table records by the current search selections.
Secondly, you have see if there are any Qualified Links to the main table record you are viewing.
If not, create the Qualified links in Data manager, for the main table record and the Qualified Table Record.
Once this is done, you will see the Display fields of the Qualified table for which the links exists for the given main table record.
Message was edited by:
Adhappan Thiagarajan

Error while trying to modify a Qualified Lookup Value.

Hello,
I have the following structure:
Vendor <-- Main Table
vendorName
vendorType
BankDetails <-- Qualified Table
BankDetails (Table)
Country (non-qualifier value)
bankKeyCode (cualifier value)
Country
code
name
I am trying to modify the BankDetails for a specific Vendor, I am getting a Record from Country table and then create a Link for the QualifiedLookupValue
qualifiedLookupValue = (QualifiedLookupValue) mainRecord.getFieldValue(bankDetailFieldId);
int index = qualifiedLookupValue.createQualifiedLink(countryRecord.getId());
qualifiedLookupValue.setQualifierFieldValue(index, bankKeyFieldId, new LookupValue(bankKeyRecord.getId()));
mainRecord.setFieldValue(bankDetailFieldId, qualifiedLookupValue);
And then I modify the main Record (Vendor).
I am getting the error: com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: Server error (0xffaa6000)
What I have found in the forum is that this error is related to "Record Not Found". However, I am actually getting a correct Country from the Country table.
Any Idea?.
Many thanks in advance.
Best Regards,
Baez

Hi Baez,
You have to create a record with country record id in BankDetails table or get record id if country record id is already existed in BankDetails table and use this record id to create qualified link .
1. get Country record id
2. search in Bankdetails table with Country Record id,
3 . if exist in Bank details table, get record id in Bank details table and pass it to createQualifiedLink()method
or
3. if Country record does not exist in BankDetails table, then create new record in bankdetails table with Country record id, pass record id of new record to createQualifiedLink()method
I hope this helps you......
Cheers,
Veeru

Error while inserting value Qualified field in the main table

Hello,
I am trying to populate Qualified field in the main table when a new record is inserted in the Products Repository.
The field is Reference Price and its a qualified lookup field. I am using the below code to create qualified lookup value and create qualified link values.
QualifiedLookupValue qlvRefPrice = new QualifiedLookupValue();
TableId qltabid = repSchema.getTableId("ReferencePrices");
FieldId qlfieldid = repSchema.getFieldId("ReferencePrices","RP_ReferncePrices");
RecordId rdRefPrice = getRecordId(connPool,session,"RP",qlfieldid,qltabid);
HashMap map = new HashMap();
map.put(repSchema.getFieldId("ReferencePrices","StartDate_ReferencePrice"),new DateTimeValue(cal));
map.put(repSchema.getFieldId("ReferencePrices","EndDate_ReferencePrice"),new DateTimeValue(cal));
map.put(repSchema.getFieldId("ReferencePrices","ListPrice"),new FloatValue(Float.parseFloat("123.3")));
map.put(repSchema.getFieldId("ReferencePrices","Currency"),new LookupValue(getLookupRecordId(connPool,session,"Currencies","Currency_Currencies","EUR")));
QualifiedLinkValue qlvLinkValue = MdmValueFactory.createQualifiedLinkValue(rdRefPrice,map);
qlvRefPrice.addValue(qlvLinkValue);
emptyRecord.setFieldValue(fieldIdRefPriceHistory,qlvRefPrice);
However when the createrecord command is executed I get the following error.
java.lang.RuntimeException: No matching validation Id 97. at com.sap.mdm.internal.validation.ValidationInfoHelper.retrieveValidations(ValidationInfoHelper.java:71) at com.sap.mdm.data.commands.CreateRecordCommand.execute(CreateRecordCommand.java:246) at com.alcatel_lucent.productdetail.ProductItemDetail_Comp.createProduct(ProductItemDetail_Comp.java:2927) at com.alcatel_lucent.productdetail.wdp.InternalProductItemDetail_Comp.createProduct(InternalProductItemDetail_Comp.java:656) at com.alcatel_lucent.productdetail.ProductItemAddView.onActionSave(ProductItemAddView.java:971) at com.alcatel_lucent.productdetail.wdp.InternalProductItemAddView.wdInvokeEventHandler(InternalProductItemAddView.java:662) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869) at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77) at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1356) at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327) at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:869) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
I spoke to my MDM team and they say there is no validation which they have put for Reference Price field. I have tried inserting values in another field of type qualified lookup in the same main table and that works without any issue.
The code is as below:
QualifiedLookupValue qlvRating = new QualifiedLookupValue();
TableId qlvtable = repSchema.getTableId("ProductRatings");
FieldId qlvratinglink = repSchema.getFieldId("ProductRatings","RatingLink");
RecordId rdidPR = getRecordId(connPool,session,"CI",qlvratinglink,qlvtable);
wdComponentAPI.getMessageManager().reportSuccess("rdidPR "+rdidPR);
HashMap mapPR = new HashMap();
mapPR.put(repSchema.getFieldId("ProductRatings","AvailRating"),new LookupValue(getLookupRecordId(connPool,session,"AvailabilityRatings","AvailabilityRating_AvailabilityRatings","CI")));
mapPR.put(repSchema.getFieldId("ProductRatings","EffectiveDate"),new DateTimeValue(cal));
mapPR.put(repSchema.getFieldId("ProductRatings","FERAIndic"),new LookupValue(getLookupRecordId(connPool,session,"ReplacementIndicators","Code","FE")));
mapPR.put(repSchema.getFieldId("ProductRatings","FERAOrdItem"),new LookupValue(getLookupRecordId(connPool,session,"ReplProducts","ProdID","100008200")));
QualifiedLinkValue qlvLink = MdmValueFactory.createQualifiedLinkValue(rdidPR,mapPR);
qlvRating.addValue(qlvLink);
emptyRecord.setFieldValue(fieldIdRatingHistory,qlvRating);
I would really appreciate if someone can help in solving the issue.
Thanks in advance,
Aamod

Hi Aamod,
Sees that some validation/assignments are getting triggered as soon as you make changes to the record in MDM. Please check once after removing validations/workflow that you may have. This way you may debug the issue.
Hope this helps!!
Cheers,
Arafat

Workaround on all the limitations of Qualified Lookups, Multivalued Tuples.

Dear Experts,
As we all know, there are lots of limitations on Qualified Lookups in MDM 5.5 and also in MDM 7.1....
1) Can't write Assignments...
2) Failed validation won't specify which qualified link has failed.
3) Compare records won't show link wise comparison of qualified links.
4) Can't start qualified link level workflows.
5) Role level constraints not applicable for Qualified lookup and tables referencing from QL directly or indirectly.
6) Qualified link level check-in check-out operations are not possible.
7) Qualified link level unique constraints are not possible (this becomes pain if links get duplicated by mistake)
8) Duplication of QL link is not allowed in data manager (for copying Qualifier values in new Qualified link).
9) Tuple is replacement for qualified lookup, but its more restrictive than QL (validation are not allowed on multivalued tuple).
10) ....... many more (which might have discovered by you all)
What if we make all the qualified lookups as main table and link those table to actual main table using Lookup [ Main] field type?
Well it will restrict the data analysis objective which is one of goal of Master Data Management...
But this will solve all the problems and limitations due to Qualified Lookup or Multivalued Tuple!
I think its feasible and technically possible (But only in MDM 7.1 onward)
How is the IDEA !!!
Thanks & Regards,
- Shailesh.

Dear Michael,
Thanks for your valuable replay...
Well out of 9 pain points I listed above...
Some of them may be fixed in future releases...
But there are some points which (I feel) may not be on the feature list of future releases like....
2) Failed validation won't specify which qualified link has failed.
3) Compare records won't show link wise comparison of qualified links.
4) Can't start qualified link level workflows.
6) Qualified link level check-in check-out operations are not possible.
(all these points are applicable for tuples also)
Above points can be ignored at the time of fresh implementation
But its become blocker in new scenarios which are taken-up after go-live! (i.e expansion of already live repository)
Most of the people in MDM might not be aware of that import works on a single main table at a time.
Well you are an expert, what you said is something new and useful... Thanks for that !
Thanks & Regards,
Shaailesh.

Qualified lookup table

Hi Guys,
Can you tell me the steps to be followed for importing and syndicating qualified lookup table .
Thanks,
MS Reddy

Hi,
1. Import all the lookup tables used in Qualified table.
2. Import qualified table data along with main table data only. For more than one qualified table record you should have repeated main table record.
E.g.
Qualified Table - Price Information
Lower Bound
Purchasing Info Record ID
Purchasing Organization
Amount
Currency
First three fields are the non-qualifiers amongst which Purchasing Organization is the lookup field. So you need to first populate this field.
Now your main table record is
Supplier     Supplier Part Number     Short Description     Product ID     Service Item     Lower Bound Purchasing Info Record ID     Purchasing Organization     Currency     Amount
AGENCY01          1000               metal processing     IBG-100               False     1     5300000018     Mumbai Purchase Org     Indian Rupee     100.00
1. Map all the main table fields
2. Identify the Display fields of your Qualified table, if your qualified table has more than one Display field then map the fields with the fields marked as D in destination structure e.g. in above given table all the three non-qualifiers are the display fields then mark Lower Bound with the D   Lower Bound field, similarly map the other display fields
3. Select all the Display fields at source side, right click and select Create Compound field. This will combine your input fields and automatically map them with Qualified field.
4. Map the qualifiers
5. Select the unique fields in Matching fields tab and execute the import.
When you syndicate data containing qualified links, it will create the number of output records depending on the number of qualified links.
Regards,
Jitesh Talreja

Qualified Lookup Table in Webdynpro Content Generator

I am trying to build a user interface with the webynpro component generators from the business content deployed on the portal. The problem I face is with qualified lookup tables. From the main table, there is an embedded table which contains the qualified lookup table. I can press the "edit" button to open a pop-up window which shows the details of the qualified link. Unfortunately, on MDM 7.1 SP05, the pop-up window contains a table at the top of the screen that forces the entire window to span the width of the table, which will go on quite far because I have about 20 fields in my qualified lookup table. Below I can enter the values for the individual fields, but it is difficult to use because you have to scroll all the way to the right to select drop down values. Is there a way to remove the summary table from the pop-up window for qualified lookup tables? I havent seen an option in the UI config.

Apparently you can configure the fields that are shown in the pop-up window, but it also limits the fields that are displayed on the iView of the main table.

Qualifier table option in import manager.

Hi Sdners,
I want ot know what is usability of "Set Qualified Update" option in menu bar of import manager.
How to use above mentioned option because when im trying to use it, its greyed out.
Iam using MDM 5.5 SP04.
Explain with below mentioned example.
Main table:
1)Material_number -
> Integer
2)Material_description -
> Text
3)Region -
> LookUpQualified(multivalued).
Qualified Table.
1)Region -
> Nonqualifier.
2)Tax -
> Nonqualifier.
3)Price -
> Qualifier.
Points will be rewarded for genuine answere.
Thanks in Advance.
Regards,
Neethu Joy.

Neethu,
Here's the scenario where you would use this option.
Suppose you are importing the main table data and qualified table data. The initial load will go fine and you will see correct data in the main table and in the qualified table. However, if you are loading the same data again (somebody made some changes and now the client wants you to re-import the data) then you should be very careful with the qualified data. By default a qualified link is set to 'Append' which means every time you import data (even the same data), import manager will create a new link in the qualified tables. To avoid this, you choose the option 'Update' instead of append. This option will allow you to update the existing links and create new ones ONLY if there is new data for them.
Now about why the option is grayed out. To enable this option you have to right click the field that links the qualified table to the main table. For example, in your example below, the field 'Region' is the link between the qualified table and the main table. Right click on this field to set the import option.
Regards,
T

Can MDM Web Services return qualifier values?

We are running MDM 5.5 SP06 Patch04 (we will be doing a technical upgrade to MDM 7 later this year).
I am investigating the MDM web services and came upon a potential problem. In the test harness, I searched for a record, specifying ALL for the result definition and everything seemed to come back except qualifiers; lookup values came back, taxonomy values came back, qualified lookup display values came back, qualified link ids came back, but no qualifier values.
I searched again on the qualified link record ids in the qualified lookup table and I got the non-qualifiers, which is the expected behavior. The qualifiers have to come back with the main table record, though.
Are qualifiers not fully supported in the MDM 5.5 web services, or am I not searching properly?
Thanks for any help you can provide.
Doug

Hi Doug
For me all are working good.
Can you look at pages 24-26 from "Portal content development guide"
https://websmp201.sap-ag.de/~sapidb/011000358700001119612007E
Regards
Kanstantsin

Database link not working properly

I have to link to another database...I have created an entry in my TNS names on the oracle server and have used the following script to create the link:
CREATE PUBLIC DATABASE LINK DATA
CONNECT TO USERNAME IDENTIFIED BY PASSWORD
USING 'DATA';
Data is the name of the database sid, and I am able to connect to the server using the username/password@sid in sqlplus. Oracle tells me that the link is created successfully, however if I try to describe user_tables@data I get the following error:
SQL> desc user_tables@data;
ERROR:
ORA-02085: database link DATA connects to DATA.WORLD
Please help!
Jes

You will see this error when the global name of the remote database does not match what you have in your link. Although the link name might match the SID, the fully qualified link name does not.
You can either:
1) Set the GLOBAL_NAMES parameter to FALSE in the database in which you have created the database link.
2) Recreate the link so that the full link matches the global name of the remote db (query GLOBAL_NAME in the remote db if you don't know it)
Good luck!

Add Non-Standard Web Link in Mac Mail

Does anyone know how to add a non-standard web link? The add link dialog box does not like my url.
I need to add a link like this: http://someserver100/index.html.
It disables the "OK" button as soon as I add the "100" after "someserver".
Prior to the Leopard upgrade I never had a problem doing this. Now it seems that Mail is trying to be too clever. Please help, this is an important business need for me to be able to send links like this.

I didn't originally go deep into detail as not to bore, but maybe the details will make the difference.
I am a web developer. I have a client that I vpn into to make web updates. The server that I work on is a testing / development server, not the outside world facing production server. The server is not viewable via a domain name. So I can not get to it by typing www.domainname.com. Instead, the client's IT guys have a host name set up for the server that I need to use due to some of the back end technology that serves the pages.
The server name is "development100".
In order for me to view pages on this server, I had to make an entry in my host file so my browser would know what ip address "development100" is associated with. That way whenever I type "http://develoment100" into my browser's url bar to proof my web work it would resolve me to the testing / development server.
Now, once my changes are done and posted, I need to send a notification email to the IT staff that servers two purposes. First, it gives them an exact url laundry list of what files have have updated. Second, it gives them a link to click for each item that will allow them to proof that html, jpeg, etc.
A typical item in this list would like like this: http://development100/index.html
That link should send them directly to the index page on the server for example. I have be using this system of building the notification emails with these links for over five years and prior to upgrading to Leopard, it always worked.
Now, if I try to "Add Link" and type "http://development100/index.html" in the dialog box. The "OK" button will become disabled as soon as I key in the first number in that link.
If I don't "Add Link" and just key "http://development100/index.html" into the body of the email the link will cut off at the first number as well. So the link will look like this: "http://development"
Sorry for the long explanation, but I think that it is necessary. The answer may just be that Apple is trying to verify / qualify links automatically and wont let numbers go in the link name without a .com / suffix. Thanks for the help.

Max no of Qualified links

Similar Messages

Maybe you are looking for