Saturday, 1 October 2011
A bored person is a boring person.
A bored person is a boring person.
Thursday, 29 September 2011
Cascade link type 'NoCascade' is invalid for Delete. while importing customizations
If rollups installing/uninstalling does not helps, try exucute this sql on your _mscrm database:
UPDATE [dbo].[RelationshipView] SET [CascadeDelete] = 2
WHERE [IsCustomRelationship] = 0 AND [CascadeDelete] = 0
UPDATE [dbo].[RelationshipView] SET [CascadeDelete] = 2
WHERE [IsCustomRelationship] = 0 AND [CascadeDelete] = 0
Crm routing check
* rollup matches?
* can import customization with out issue
* all code builds
* can import customization with out issue
* all code builds
Wednesday, 28 September 2011
New EA wiki tips and tricks
http://eawiki/TipsAndTricks.ashx
Nav Solution wiki template
Create a client page first with client short code e.g. WAIMIL
Create a solution page name in this format {client short code]_[Project Name] e.g. WAIMIL_CRM
Nav Solution wiki template
Create a client page first with client short code e.g. WAIMIL
Create a solution page name in this format {client short code]_[Project Name] e.g. WAIMIL_CRM
What to do in the handover process?
The following tells you what to do in the handover process
The main theme is that when a request coming, you know enough to do your job. where the server is. How to compile all the code? How to deploy? Know who to ask for support, e.g. infrastructure support.
Initial meeting -> Handover meetings -> Handover closer meeting
* Initial meeting. Who is who? What is our goals?
* Another way to think about it. Where is the test? The test scripts will tell the business process.
* When will the warranty period finish? Who will determine if the case come to Management Services or the Delivery team?
* Wiki page requirement: This documentation should be completed to a level where a developer could setup a development environment, make changes, test and release the changes to UAT and Live. Use the Support Handover questions to guide you in the sort of information required.
+ Where is the code in tfs
+ Grant us sufficient tfs permission and remove permission of developer.
* We must retain all project documentation plus the dev environment. Not allow the delivery team to delete anything.
* Dev environment - Can the dev environment be setup successfully by import customisation or import org?
* Seen through the code and see the code in action in its environment/platform
* Find out the overall business process with the requirements in mind.
* Where are the servers?
* Where are the environment?
* Solution diagram
* How do the users use the system? For example, A CERA user creates an contact -> A CETAS user ticks an assessment check box -> Hit save -> A workflow will generate a household record automatically.
* Be careful with any SHARED projects or resources.
* All the Source Code is checked in, can be built successfully and deploy successfully too. Basically, the entire source code base need to be downloaded to a separated computer and build and deploy.
The main theme is that when a request coming, you know enough to do your job. where the server is. How to compile all the code? How to deploy? Know who to ask for support, e.g. infrastructure support.
Initial meeting -> Handover meetings -> Handover closer meeting
* Initial meeting. Who is who? What is our goals?
* Another way to think about it. Where is the test? The test scripts will tell the business process.
* When will the warranty period finish? Who will determine if the case come to Management Services or the Delivery team?
* Wiki page requirement: This documentation should be completed to a level where a developer could setup a development environment, make changes, test and release the changes to UAT and Live. Use the Support Handover questions to guide you in the sort of information required.
+ Where is the code in tfs
+ Grant us sufficient tfs permission and remove permission of developer.
* We must retain all project documentation plus the dev environment. Not allow the delivery team to delete anything.
* Dev environment - Can the dev environment be setup successfully by import customisation or import org?
* Seen through the code and see the code in action in its environment/platform
* Find out the overall business process with the requirements in mind.
* Where are the servers?
* Where are the environment?
* Solution diagram
* How do the users use the system? For example, A CERA user creates an contact -> A CETAS user ticks an assessment check box -> Hit save -> A workflow will generate a household record automatically.
* Be careful with any SHARED projects or resources.
* All the Source Code is checked in, can be built successfully and deploy successfully too. Basically, the entire source code base need to be downloaded to a separated computer and build and deploy.
Sunday, 25 September 2011
Fixed my roof from leaking.
The tile is made of concrete
The Ridges are made of Mortar. Mortar is like concrete but finer.
Chimney's cap is called cowling
Edward's & hardy is only doing cleaning and re-paint which need to be re-done every three years.
Re-coating however will last 30 years. Jeremy is using a industry coating which is really good.
Cladding = external wall.
A chimney pipe is called flute. Chimney has outer flute, middle flute and internal flute.
-----Key Words / Terminology-------
Ridge
Chimney cowling
Mortar
concrete
re-coating - booking immediately after Christmas for a March job.
clean and re-spay
The Ridges are made of Mortar. Mortar is like concrete but finer.
Chimney's cap is called cowling
Edward's & hardy is only doing cleaning and re-paint which need to be re-done every three years.
Re-coating however will last 30 years. Jeremy is using a industry coating which is really good.
Cladding = external wall.
A chimney pipe is called flute. Chimney has outer flute, middle flute and internal flute.
-----Key Words / Terminology-------
Ridge
Chimney cowling
Mortar
concrete
re-coating - booking immediately after Christmas for a March job.
clean and re-spay
Saturday, 24 September 2011
How to Parallel Park
Start position: Your car should be 30 cm away from the car, will be in front of you, in parallel. The rear wheel of your car should be next to the rear wheel of the "front" car approximately.
Turn sharp to the left.
Back in slowly
Once you back passenger door is even with the rear bumper of the "front" car, turn the steering wheel back to straight up the car.
Continue reverse straightly until the curb just disappeared from your side mirror.
--OR--
Continue reverse straightly until the rear wheel facing the curb is nearly as close as the final distance desired from it (no more than 1 foot (30 cm) ultimately being desirable) and the rear end of the car is still a few feet (about a meter) from the car behind. Use the side mirror to check the position of the panel top of you rear wheel to determine you position. A rule of thumb is that if the curb disappears in the mirror when they are pointed down, you are probably too close to the curb.
Turn to the right sharply until the car parallel to the curb.
Tips:
Be careful not to cut it too soon or too quickly, as this will result in being too far away from the curb. It is much harder to adjust your position in a space when you are too far away from the curb as opposed to being too close.
If you are parking in an area with shops, take advantage of the eventual reflection of your car in shop windows.
When backing up and lining up the cars, look in the driver's side mirror, and use the sides of the cars to know exactly how far your car has gone in towards the curb. I.e. how closely you've aligned them. That view of the sides of the cars (your car and the one behind you) offers a good easy view and check to know that you've positioned the car correctly. In particular, the side of your car above the rear wheels offers the best, most accurate view of where exactly your car is.
http://www.youtube.com/watch?v=TMrO_-bsooQ&feature=player_embedded
http://www.videojug.com/film/parallel-parking-4
Turn sharp to the left.
Back in slowly
Once you back passenger door is even with the rear bumper of the "front" car, turn the steering wheel back to straight up the car.
Continue reverse straightly until the curb just disappeared from your side mirror.
--OR--
Continue reverse straightly until the rear wheel facing the curb is nearly as close as the final distance desired from it (no more than 1 foot (30 cm) ultimately being desirable) and the rear end of the car is still a few feet (about a meter) from the car behind. Use the side mirror to check the position of the panel top of you rear wheel to determine you position. A rule of thumb is that if the curb disappears in the mirror when they are pointed down, you are probably too close to the curb.
Turn to the right sharply until the car parallel to the curb.
Tips:
Be careful not to cut it too soon or too quickly, as this will result in being too far away from the curb. It is much harder to adjust your position in a space when you are too far away from the curb as opposed to being too close.
If you are parking in an area with shops, take advantage of the eventual reflection of your car in shop windows.
When backing up and lining up the cars, look in the driver's side mirror, and use the sides of the cars to know exactly how far your car has gone in towards the curb. I.e. how closely you've aligned them. That view of the sides of the cars (your car and the one behind you) offers a good easy view and check to know that you've positioned the car correctly. In particular, the side of your car above the rear wheels offers the best, most accurate view of where exactly your car is.
http://www.youtube.com/watch?v=TMrO_-bsooQ&feature=player_embedded
http://www.videojug.com/film/parallel-parking-4
Subscribe to:
Posts (Atom)

